Skip to content

Add blurb about bypassing rulesets #30

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

Merged
lcarva merged 1 commit into from
Sep 25, 2023
Merged

Add blurb about bypassing rulesets #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,3 +20,10 @@ ruleset](https://docs.github.com/en/repositories/configuring-branches-and-merges
at the organization level. This is not done automatically. When adding a new workflow, be sure to
also update the corresponding ruleset
[here](https://github.com/organizations/enterprise-contract/settings/rules).

An existing ruleset may prevent direct pushes to the default branch, e.g. `main`, for a variety of
reasons. Although pushing a commit directly to `main` is not recommended, certain occasions require
it. For example, it is not possible to create a pull request targeting a brand-new empty repository.
In such cases, add a temporary exception target for the corresponding ruleset. Remember to revert
this change. Alternatively, avoid creating empty repositories altogether by always choosing to
include a license.