Repository navigation
chore: sync main into staging - #2282
Merged
Merged
Conversation
…ead(s)) (#2269) Co-authored-by: fedcourtsai-dev[bot] <297417130+fedcourtsai-dev[bot]@users.noreply.github.com>
data(summaries): 144 plain-language case summaries
Co-authored-by: fedcourtsai-dev[bot] <297417130+fedcourtsai-dev[bot]@users.noreply.github.com>
Co-authored-by: fedcourtsai-dev[bot] <297417130+fedcourtsai-dev[bot]@users.noreply.github.com>
…ead(s)) (#2283) Co-authored-by: fedcourtsai-dev[bot] <297417130+fedcourtsai-dev[bot]@users.noreply.github.com>
data(summaries): 1 plain-language case summary
This branch was successfully deployed
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
1 participant
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.
Routine catch-up so staging keeps containing main, opened by the scheduled
sync-stagingworkflow. See that workflow header for why this runs on aschedule rather than at promotion time.
main is 18 commit(s) ahead: the deterministic writers and the bot
lanes commit there directly and never ride staging.
Merge with a merge commit, never a squash — the promotion gate asserts that
main is an ancestor of staging, and a squash would rewrite the merged history
and break that. Auto-merge is armed to do exactly that once
gateandpathspass; if it never fires, this merge conflicts and needs resolving here.