X Tutup
The Wayback Machine - https://web.archive.org/web/20220707041425/https://github.com/github/docs/issues/18936
Skip to content
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.

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

Explain different default contexts (fx with and without branch protection) #18936

Open
1 task done
alexgenaud opened this issue Jul 5, 2022 · 1 comment · May be fixed by #18935
Open
1 task done

Explain different default contexts (fx with and without branch protection) #18936

alexgenaud opened this issue Jul 5, 2022 · 1 comment · May be fixed by #18935
Labels
content

Comments

@alexgenaud
Copy link

@alexgenaud alexgenaud commented Jul 5, 2022

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches

What part(s) of the article would you like to see updated?

Some note regarding "default" behavior explicitly, would be helpful.

The documentation may be strictly correct, but certain assumed or non-obvious interpretation of "default" is likely confusing (it was for me). I assume "default" means "always without any overriding setting there is one and only one presumed value". To my surprise, "default" is contextual and may mean the exact opposite in different contexts.

The specific example I ran into (though there are numerous examples):

By default, in both git and github, 'git push --force' is allowed, even to master.
However, with branch protection enabled, then by default 'git push --force' is not allowed, by default.
The documentation clearly states that allow_force_pushes = false is default.
But it's only default in that context and not default (opposite default) in the default context (no branch protection).

Additional information

No response

@alexgenaud alexgenaud added the content label Jul 5, 2022
@welcome
Copy link

@welcome welcome bot commented Jul 5, 2022

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage label Jul 5, 2022
@alexgenaud alexgenaud linked a pull request Jul 5, 2022 that will close this issue
5 tasks
@cmwilson21 cmwilson21 linked a pull request Jul 5, 2022 that will close this issue
5 tasks
@cmwilson21 cmwilson21 removed the triage label Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
X Tutup