Skip to content

Allow locking branch in protected namespaces #709

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

Closed
isc-pbarton opened this issue Feb 19, 2025 · 1 comment · Fixed by #733
Closed

Allow locking branch in protected namespaces #709

isc-pbarton opened this issue Feb 19, 2025 · 1 comment · Fixed by #733
Assignees
Labels
customer Based on customer feedback (as opposed to something identified by developers) good first issue Good for newcomers

Comments

@isc-pbarton
Copy link
Collaborator

If a namespace is a "protected namespace" in the HCC recommended source control workflow, it should always be tracking one branch. But it's easy to forget which namespace you're in and use the source control menus to switch branch.

Idea: add a new namespace-level setting "lock branch". If this is enabled, the New Branch and Switch Branch options in the source control menu should be disabled.

@isc-tleavitt isc-tleavitt added the customer Based on customer feedback (as opposed to something identified by developers) label Feb 24, 2025
@isc-pbarton isc-pbarton added the good first issue Good for newcomers label Feb 24, 2025
isc-ksaduest pushed a commit that referenced this issue Apr 2, 2025

Unverified

This user has not yet uploaded their public signing key.
isc-pbarton pushed a commit that referenced this issue Apr 8, 2025
isc-pbarton added a commit that referenced this issue Apr 8, 2025
…ce-control into Issue-#709
isc-pbarton added a commit that referenced this issue Apr 11, 2025
@isc-pbarton isc-pbarton linked a pull request Apr 11, 2025 that will close this issue
@isc-pbarton
Copy link
Collaborator Author

Resolved by #733

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer Based on customer feedback (as opposed to something identified by developers) good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants