Search results for: Pull Request

GitHub Desktop 3.0 is bringing a closer integration with GitHub pull request workflows. Real-time desktop notifications: Pull Request Reviews: You know right away when your PR is approved, you need…

When a new issue or pull request is created and not yet submitted, the assignees, reviewers, labels and projects will all be preserved upon page refresh.

Previously, GitHub’s web UI did not allow deleting a branch that was associated with an open pull request. Now you can delete such a branch from the UI. However, doing…

Today, we are announcing the beta of the new file tree experience for pull requests! Jump between files more quickly Understand the size and scope of the change before you…

The Update branch button on the pull request page lets you update your pull request’s branch with the latest changes from the base branch. This is useful for verifying your…

We have introduced a new policy setting that controls whether GitHub Actions can approve pull requests. This protects against a user using Actions to satisfy the “Required approvals” branch protection…

GitHub Desktop now supports reviewing the statuses of individual check runs for a pull request directly in GitHub Desktop. This includes statuses of job steps for check runs generated through…

Code navigation is now available in PRs, and code navigation results for Python are now more precise.

GitHub Mobile now supports push notifications for pull request review activities – you will get notified when someone approves, comments, or requests changes on your pull requests. GitHub Mobile also…

Administrators can now allow specific users and teams to bypass pull request requirements. For context, this image shows how administrators can use branch protections to require pull requests for all…

The “Only notify requested team members” setting can now be enabled independently of “Enable auto assignment” in the Team’s code review settings. This is useful in scenarios where many users…

You can now require that all changes to a protected branch are made using a pull request, but without requiring reviews. This can be useful when you want to use…

Pull Request Merge Queue is now available in limited beta. Learn more about the feature and how to request early access. Why a merge queue? Maintaining high velocity and keeping…

The diff setting to hide whitespace changes in the pull request Files Changed tab is now remembered for you for that pull request. You no longer need to re-enable it…

Filtered files on the Pull Request Files Changed tab are now completely hidden from view (not just collapsed). This helps decrease distractions and lets you focus on just the files…

Code scanning runs analysis tools that scan your code on the triggers defined in your .yml Actions workflow file. The default CodeQL workflow analyzes your code each time you push…

You can now easily find all alerts associated with your pull request with the new pull request filter on the code scanning alerts page. To show all the code scanning…

The new Required Conversation resolution branch protection rule and Conversations menu is now generally available. Easily discover your pull request comments from the files changed tab and require that all…

With the latest version of Octicons, the states of an issue and pull request are now more visually distinct so you can scan status more easily. Learn more about Primer,…

You can now configure which code scanning alert severity levels cause a pull request check to fail. This lets you prevent pull requests that generate alerts with chosen severity levels…

On GitHub today, half of all pull request review conversations are left unresolved prior to merging. Now it is easier for authors to discover unresolved comments from the conversations menu…