Yet another commit checker on multiple projects

Bhushan Nagaraj
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 11, 2018

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

1 answer

0 votes
Julius Davies _bit-booster_com_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 13, 2018

 

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:

 

control-freak-top.png

 

 

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).

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events