Repository navigation
docs: merge main back into develop after each stable release - #101
Merged
Merged
Conversation
Squashing develop into main makes a commit develop never has, so the next release PR conflicts even with identical files (PR 98). Document the back-merge PR, merged with a merge commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
mainintodevelopand merge it with Create a merge commit, the one PR that isn't squashed. Explains why: a squash intomainmakes a commitdevelopnever has, so the nextdevelop→mainPR conflicts even with identical files (mazillka/deckyhub-plugin#98).The repository now allows merge commits (it was squash-only) so this PR can be merged that way. Feature and release PRs stay squash by convention.
🤖 Generated with Claude Code