If enabling YACC at the global level, would it also be applied to private and forked repositories?
Are there any tips to manage this at scale on large instances? 1000 of repositories where we need to apply yacc only on certain projects.
https://marketplace.atlassian.com/apps/1211854/yet-another-commit-checker?hosting=server&tab=support
Yes, the moment the YACC global config is enabled it applies to all repos, including all personal forks. But admins can override the global settings by enabling and configuring the hook itself per repository. (Note: but disabling the hook at the repository level enables the global settings if they are in force!)
I think the Control Freak add-on is better for this scenario, since its override model is more flexible, and can be set globally, per-project, and per-repo:
Just like YACC, Control Freak can block commits that don't properly reference JIRA issues.
YACC can work, but I think it will take a lot of mouse clicks!
(Full disclosure: we maintain Control Freak).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.