Pipeline Graph: Update graph state selection

changed milestone to %13.11

added DEPRECATE_pipeline dag Deliverable FY22Q2 candidate13.11 devopsverify grouppipeline authoring sectionops typefeature workflowplanning breakdown + 1 deleted label

added frontend label

	1 Warning
	This merge request changed files with disabled eslint rules. Please consider fixing them.

2 Messages

CHANGELOG missing:

If you want to create a changelog entry for GitLab FOSS, run the following:

bin/changelog -m 59685 "Pipeline Graph: Update graph state selection"

If you want to create a changelog entry for GitLab EE, run the following instead:

bin/changelog --ee -m 59685 "Pipeline Graph: Update graph state selection"

If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

We are in the process of rolling out a new workflow for adding changelog entries. This new workflow uses Git commit subjects and Git trailers to generate changelogs. This new approach will soon replace the current YAML based approach.

To ease the transition process, we recommend you start using both the old and new approach in parallel. This is not required at this time, but will make it easier to transition to the new approach in the future. To do so, pick the commit that should go in the changelog and add a Changelog trailer to it. For example:

This is my commit's subject line

This is the optional commit body.

Changelog: added

The value of the Changelog trailer should be one of the following: added, fixed, changed, deprecated, removed, security, performance, other.

For more information, take a look at the following resources:

If you'd like to see the new approach in action, take a look at the commits in the Omnibus repository.

Disabled eslint rules

The following files have disabled eslint rules. Please consider fixing them:

app/assets/javascripts/pipelines/components/graph/graph_component_wrapper.vue

Run the following command for more details

node_modules/.bin/eslint --report-unused-disable-directives --no-inline-config \
  'app/assets/javascripts/pipelines/components/graph/graph_component_wrapper.vue'

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.