Collaboration tools

What’s changing?

As part of our effort to help optimize activity feed load times and reduce timeouts, we’re migrating the organizational feed to a newer infrastructure. This migration from our existing system to an improved infrastructure will enable us to have a more performant experience for all users interacting with the organizational feed.

While this change is primarily back end, with minimal impact to the user experience, organizational feed users may notice a slight change to the UI. In our current experience, push event activity notifications have one line per event, mixed in with other event types in the feed. With this improvement, users can see all push events grouped into one card, sorted in chronological order with the most recent events appearing first.

When is the change occurring?

This change will occur on April 21st, 2025 for all users that interact with the organizational feed.

Where can I experience this?

You can see these changes on the organizational feed.

The refreshed commit details page is now generally available!

This improved page lets you view and navigate the changes within a commit with improvements to filtering, commenting, and keyboard navigation.

What’s new 🎉

• Comment counts in tree: Easily spot files with comments by seeing the number of comments directly in the file tree.
• Floating comments: Code comments now float on top of the diff to improve readability of the diffs. Click the commenter’s avatar on the right side of the line to open.
• Instantly switch views: Switch between unified and split views without waiting for the page to reload.
• Keyboard navigation in diffs: You can now navigate around changed lines in the diff using the up and down keys on your keyboard. A new context menu also makes it easier to comment, copy, and select.
• Filtering: You can filter changes by file name or extension. Also, the diffs for filtered out files are hidden to help reduce distractions.

Fixes and enhancements

Feedback during the public preview really helped us improve this page. Some of the more notable enhancements:

• Compact line height: New user setting that controls the height of lines in the diff, which can help reduce scrolling and improve readability.
• Submodule changes: The files changed when updating a submodule reference are now listed again.
• Full commit message: The full commit message was previously hidden behind “Show More”, but is now fully shown.

Some of the more notable bugs that were addressed:

• Fixed: The native browser context menu replaced by a custom menu when right-clicking on a diff.
• Fixed: Tab indents not rendering correctly on some browsers.
• Fixed: Missing “no newline at end of file” indicator.
• Fixed: Performance issues on some browsers when interacting with the page.

See the full list of fixes and enhancements in the public preview feedback discussion.

Get help

To learn more about viewing commits, see About commits.

To give feedback, ask questions, or report a bug join us in the GitHub Community.

The improved merge experience on the pull request page is now generally available! This update is designed to help you better understand the state of your pull request and get it merged faster.

This experience supports all the usual ways of merging: direct, bypass and merge, auto-merge, and merge queue, and works with rulesets to ensure pull requests meet all the requirements to merge.

What’s new

The new experience is designed to feel familiar, but also improves on the previous experience. Here are some highlights:

• Checks grouped by status: checks are now grouped by status with failing checks prioritized at the top of the list, making it easier to identify problems that need attention
• Checks ordered logically: status checks are now ordered using natural ordering to make it easier to find a specific check, especially when the list gets long
• Improved rule enforcement: errors resulting from failing commit metadata rules (like invalid commit messages) are now reported at the point of merging so they can be corrected
• Improved accessibility: consistent keyboard navigation, focus management, and landmarks help make the experience more accessible to everyone

Get help

Learn more about merging a pull request.

To suggest a feature, report a problem, or discuss this improved experience, visit the GitHub Community.

We’ve updated the contributors and code frequency repository insight views to improve navigation, allow hiding a series by interacting with the chart legend, and enable viewing and downloading the data as a CSV or PNG.

Contributors

• Keyboard-navigable date range selector: You can select date ranges using either your mouse or keyboard for improved accessibility. The available date ranges remain weekly (Sunday to Sunday), and we will only display contributors active within the selected timeframe.
• Shareable URLs for specific views: The URL now reflects the selected time period, making it easy to share or bookmark a particular view.

Code frequency

• The two axes are now differentiated by line style as well as color.
• Data points are navigable and show more detail in a tooltip. Previously, you could only reference the axes visually.

Join the discussion in GitHub Community.

The refreshed pull request commits page, which was previously in public preview, is now generally available! This updated page improves performance, is more consistent with other pages across GitHub, and is accessible to more users.

Your feedback during the public preview helped us deliver a better experience, including better keyboard navigation. If you have additional feedback, please let us know in the GitHub Community.

Repository rules now allow you to enforce which merge methods are available when merging pull requests into a specified branch. The merge method rule is available for rulesets at the repository, organization and the enterprise level. Allowing you to choose between merge commit, squash, or rebase to ensure only the selected merge methods are allowed on the targeted branches across the user interface and APIs.

Learn more in the documentation and join the discussion within GitHub Community.

To help you better understand the state of your pull request and get it merged faster, the merge experience on the pull request page has been improved! This experience is currently in public preview.

What’s new

We’ve maintained the familiar look of the existing merge experience while incorporating several usability improvements:

• Checks grouped by status: checks are now grouped by status with failing checks prioritized at the top of the list, making it easier to identify issues that need attention
• Checks ordered alphabetically: status checks are now ordered alphabetically to make it easier to find a specific check
• Commit metadata validation: errors from failing commit metadata rules (like non-compliant commit messages) can now be corrected and retried
• Improved accessibility: consistent keyboard navigation, focus management, and landmarks help make the experience more accessible to everyone

For a more complete list of changes visit the feedback discussion.

Try it out

This improved experience is rolling out gradually and is turned off by default. Once it becomes available to you, a Try the new merge experience link will appear below the merge box on the pull request page:

Click it to switch to the improved experience. A link is also available for easily switching back to the existing experience. You can also toggle the experience via the feature preview dialog.

Known issues

As this experience is in public preview, you may run into some bugs and missing features (let us know when you do). Some of the known issues include:

• Actions workflows requiring approval cannot be approved currently
• Changing the commit author email when merging is not currently supported

For a more complete list of known issues visit the feedback discussion.

Feedback

We want to hear from you! To provide feedback, ask questions, and see a list of known issues, visit the GitHub Community improved merge box discussion!