Repository navigation
Conversation
…are case that needs one
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.
flyloft now squash-merges the tool pull requests its campaigns open (brineylab/flyloft#297), so the shed's instructions say the same for people:
gh pr merge --squash. The repository still allows merge commits and rebase merges, so a case that needs one can still use it.promoteis unaffected: it computes the candidate tag from the tree of the commit that lands onmain, andmain's up-to-date rule makes that the tree that was built and tested. hello 1.0.1 (#51) was squash-merged by flyloft and promoted this way.Changes:
AGENTS.mdandCONTRIBUTING.md(the merge instruction), and two sentences indocs/DESIGN.mdthat described flyloft's merge.