docs: Update CONTRIBUTING for squash-merge workflow #1862
Merged
Conversation
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
We now always use the squash-merge workflow. Simplify the documentation on crafting a good commit message or PR description to only talk about the PR description. #1824
|
Play this branch at https://play.threadbare.game/branches/endlessm/wjt/docs-update-contributing-for-squash-merge-workflow. (This launches the game from the start, not directly at the change(s) in this pull request.) |
manuq
approved these changes
Jan 25, 2026
Comment on lines
+116
to
+119
| Your pull request will be squashed into a single commit when it is merged, and | ||
| the title and description of the pull request will be used as the commit | ||
| message. If you want to make several separate changes, open a separate pull | ||
| request for each one. This is subjective, so use your judgement! |
manuq
deleted the
wjt/docs-update-contributing-for-squash-merge-workflow
branch
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.
docs: Update CONTRIBUTING for squash-merge workflow
We now always use the squash-merge workflow. Simplify the documentation
on crafting a good commit message or PR description to only talk about
the PR description.
#1824