pull-requests

Subscribe to all “pull-requests” posts via RSS or follow GitHub Changelog on Twitter to stay updated on everything we ship.

~ cd github-changelog
~/github-changelog|main git log main
showing all changes successfully

We are shipping improvements to pull request workflows on GitHub Mobile, making reviewing and merging pull requests much easier on the go!

  • The pull request description has been moved into the header, providing quick context about the changes without having to scroll to the timeline. Longer descriptions are truncated and can be expanded inline with a tap.
  • We brought the merge box designs more closely in line with GitHub.com. By using clear colors and iconography, it is easier to scan through the overall status of a pull request to understand the current state of reviews, checks, and overall mergeability.
  • We added a contextual call to action in the Files Changed cell that will help people understand when their review is required, or when new changes have been pushed to the pull request since their last review.
  • When reviews and checks are passing, pull requests can be merged directly from the view without having to open new dialogs. We've also built a fun animation that plays during a merge which will make working on the go feel more satisfying!


Read more about GitHub Mobile and send us your feedback to help us improve.

See more

Pull request and review-related events are now included in the audit log at both the enterprise and organization levels. This helps administrators better monitor pull request activity and ensure security and compliance requirements are being met.

Events now included in the audit log:

  • A pull request is created, merged, closed, reopened, converted to draft, or marked ready for review
  • A review is requested or a request is removed
  • A review comment is added, updated, or deleted
  • A review is submitted, dismissed, or deleted

Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For example action:pull_request filters for events directly on a pull request, action:pull_request.merge shows just merge events, and action:pull_request_review shows review events.

Learn more about audit log and available pull request actions

See more

To prevent unexpected changes from potentially slipping in after auto-merge is enabled on a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository.

Note: users without write access can still update their pull requests to bring in changes from the base branch without having auto-merge disabled, but auto-merge will be disabled if the update results in merge conflicts that have to be resolved. This is to prevent merge-conflicts being deliberately used as a way to introduce code that hasn't been fully reviewed by the people with write access to the project.

Learn more about automatically merging pull requests when all merge requirements have been met.

See more