Skip to content

Document where admin-bypass of branch protection can be used. #16

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Document where admin-bypass of branch protection can be used. #16

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
6 changes: 6 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,12 @@ in your pull request. Alternatively, to signoff a bunch of commits you can use `
All changes which are to be committed in project source control must be reviewed by at least one Code Owner before being merged.
If the change is being authored by someone who is a Code Owner, that change must be reviewed by at least one other Code Owner before being merged.

The CI workflow runs the project's unit and integration tests. All tests must pass before a PR is consider eligible for merging.

The project uses (SonarCloud)[https://sonarcloud.io/organizations/kroxylicious/projects] to help maintain code quality. In general,
all PRs must meet all the quality gates before being eligible for merge. Sometimes reasonable code changes cause spurious quality gate
failures. In these situations, discuss the issue on the PR. If agreeement is reached a Code Owner with Admin rights can bypass the protection.

## I just have a question

If you encounter any issues while using Kroxylicious, you can get help using:
Expand Down