admin: Branch protections requiring up-to-date PRs before merging #406

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

Jump to bottom

Open

jeswr opened this issue Jun 13, 2025 · 3 comments

Member

jeswr commented Jun 13, 2025 •

edited

Loading

@HolgerKnublauch @ajnelson-nist @PapoutsoglouE if you have permission to do so I strongly encourage you to enable branch protections which require PRs to be up-to-date to merge. These settings should be available at https://github.com/w3c/data-shapes/settings/branches

This prevents the #402 issue (described in #401 (comment)) recurring.

Contributor

ajnelson-nist commented Jun 13, 2025

I don't have those permissions, & it's fine for me not to be given them.

I'm fine with enabling this GitHub mechanism.

Contributor

afs commented Jun 14, 2025

@jeswr - which merge choice did you use for #402?

Member Author

jeswr commented Jun 14, 2025

Squash & merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment