Allow bypassing required pull requests

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 changes to a branch:

screenshot of option to protect matching branches

This is a good practice, but you may want to make exceptions to this rule for specific people and teams. For example, if you have an automated process that calls GitHub APIs to make changes in a repository, you may want to permit that automation to make changes without creating a pull request.

Now, when you require pull requests and their related protections for a branch, you can specify people and teams who should be free from those requirements. As shown in the image below, select Allow specific actors to bypass pull request requirements. Then, search for and select the people and teams who should be allowed to bypass the requirements.

Screenshot of option to bypass PR requirements

For more information, visit Managing a branch protection rule.

The new GitHub Issues – November 18th update

After our GitHub Issues public beta announcement at GitHub Universe, we’ve seen teams start to engage with and adopt project tables, boards and all of our recently released features. Now that we’re in the public beta, we’re going to continue to ship on the same cadence we did during private beta (every 2-3 weeks), engage with your feedback, and deliver on the feature roadmap.

Here are the latest updates which are available to all projects on GitHub.

🔀 Re-orderable views

One of the most requested features in our feedback forum, you can now easily re-order views via drag and drop to get the perfect sequence.

🏈 Team permissions

The manage settings screen now supports adding permissions directly to GitHub Teams, making it even easier to ensure everyone has the right access level needed for your projects.

✨ Bug fixes & improvements

Other changes this week include:

  • Clicking outside of the board will now de-select any selected cards on the board layout.
  • Resolved a problem where archiving all cards in a column would also archive cards filtered out. Now only visible cards will be archived.
  • To avoid confusion, we have disabled the New Field menu item when you are in the board layout.
  • Copying the contents of a board is now possible via cmd+c. To copy everything, combine this with meta+a to select all your cards.

See how to use GitHub for project planning with GitHub Issues, check out what’s on the roadmap, and learn more in the docs.

 

See more

Debugging CodeQL code scanning made easier by retaining diagnostic artifacts in Actions

It's now easier to debug problems with CodeQL code scanning: an optional flag in the Actions workflow file will trigger diagnostic data to be uploaded as an artifact to your Actions run. To do this, you can modify the init step of your Actions workflow:

- name: Initialize CodeQL
  uses: github/codeql-action/init@v1
  with:
    debug: true

The data will be uploaded as an Actions artifact named debug-artifacts, attached to the workflow run. Such artifacts contain CodeQL logs, CodeQL databases, and the SARIF files that were produced.

These artifacts will help you when you're debugging problems with CodeQL code scanning. When contacting GitHub support, they might ask for this data too.

Learn more about Troubleshooting the CodeQL workflow.

See more
View all changes