Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

repo sync #17978

Merged
merged 2 commits into from
May 18, 2022
Merged

repo sync #17978

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c7bace
Merge pull request #27802 from github/repo-sync
Octomerger May 18, 2022
fe67b3d
Add missing versioning (#27805)
lecoursen May 18, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ...requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,9 @@ Number of commits | Summary | Description |
One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit
More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order

{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}
People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".
{% endif %}

### Squashing and merging a long-running branch

Expand Down