Add offset and limit parameters to names resolver

changed milestone to %13.12

added 2 commits

b640f860 - Add offset and limit parameters to names resolver
3ddae57d - Add CHANGELOG entry

Compare with previous version

added GraphQL devopsverify featureenhancement grouppipeline authoring sectionops typefeature labels

marked the checklist item I have included a changelog entry. as completed

changed the description

added workflowin review label

mentioned in merge request !59217 (merged)

added backend documentation labels

	2 Messages
	This merge request adds or changes files that require a review from the Database team.
	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.

This merge request requires a database review. To make sure these changes are reviewed, take the following steps:

Ensure the merge request has database and databasereview pending labels. If the merge request modifies database files, Danger will do this for you.
Prepare your MR for database review according to the docs.
Assign and mention the database reviewer suggested by Reviewer Roulette.

The following files require a review from the Database team:

app/finders/repositories/branch_names_finder.rb

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! 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.

Category	Reviewer	Maintainer
backend	Alina Mihaila (`@alinamihaila`) (UTC+3, 1 hour ahead of `@matteeyah`)	Kerri Miller (`@kerrizor`) (UTC-7, 9 hours behind `@matteeyah`)
database	David Sincheol Kim (`@dskim_gitlab`) (UTC+9.5, 7.5 hours ahead of `@matteeyah`)	Steve Abrams (`@sabrams`) (UTC-6, 8 hours behind `@matteeyah`)