Add source as argument to ResolvesPipelines

added backend label

	6 Warnings
	0ebff512: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	61869224: The commit subject may not be longer than 72 characters. For more information, take a look at our Commit message guidelines.
	c7fcf8fe: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.
	e254d9c5: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.
	bb14eaae: The commit subject may not be longer than 72 characters. For more information, take a look at our Commit message guidelines.
	b3e9b17c: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

doc/api/graphql/reference/index.md

The review does not need to block merging this merge request. See the:

Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
The Technical Writer assigned for that stage and group.
Documentation workflows for information on when to assign a merge request for review.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	Reuben Pereira (`@rpereira2`) (UTC+5.5)	Heinrich Lee Yu (`@engwan`) (UTC+8)

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.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger