Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule
What part(s) of the article would you like to see updated?
In the Creating a branch protection rule section, the documentation currently says:
In the "Code and automation" section of the sidebar, click Branches.
The sidebar section name differs depending on the GitHub product:
GitHub Free, Pro, and Team (FPT): "Code, planning, and automation"
GitHub Enterprise Cloud (GHEC): "Code, planning, and automation"
GitHub Enterprise Server (GHES): "Code and automation"
The documentation should be updated to reflect this product-specific version. For example:
In the "Code, planning, and automation" section of the sidebar, click Branches. On GitHub Enterprise Server, this section is named "Code and automation."
This would make the instructions accurate for users across GitHub Free, Pro, and Team, GitHub Enterprise Cloud, and GitHub Enterprise Server, and help users locate the Branches settings more easily.
Additional information
The documentation should use the appropriate version-specific content so that users see instructions matching the UI for the GitHub version they are using.
- FPT and GHEC: "Code, planning, and automation"
- GHES: "Code and automation"
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule
What part(s) of the article would you like to see updated?
In the Creating a branch protection rule section, the documentation currently says:
The sidebar section name differs depending on the GitHub product:
The documentation should be updated to reflect this product-specific version. For example:
This would make the instructions accurate for users across GitHub Free, Pro, and Team, GitHub Enterprise Cloud, and GitHub Enterprise Server, and help users locate the Branches settings more easily.
Additional information
The documentation should use the appropriate version-specific content so that users see instructions matching the UI for the GitHub version they are using.