Repository navigation
Conversation
A merge request is READY when it is open, not a draft, carries every label in the new [ready] section and, by default, has a passing head pipeline. The `ready` column shows how long it has been READY: the later of the draft being lifted and each required label being added, read from the REST label events and "marked as ready" system notes. A pipeline re-run does not reset it. `ready = true` on a filter shows only READY merge requests, and sorting by `ready` keeps rows with no age last in either direction. Lookups are memoized per merge request on `updated_at` and seeded from the cache.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A merge request is READY when it is open, not a draft, carries every label in the new [ready] section and, by default, has a passing head pipeline. The
readycolumn shows how long it has been READY: the later of the draft being lifted and each required label being added, read from the REST label events and "marked as ready" system notes. A pipeline re-run does not reset it.ready = trueon a filter shows only READY merge requests, and sorting byreadykeeps rows with no age last in either direction. Lookups are memoized per merge request onupdated_atand seeded from the cache.