By the way, seeing you’re talking about branch rul...
# toolsm
Matthieu Muffato
05/08/2026, 11:54 AMBy the way, seeing you’re talking about branch rules, there’s a new-ish feature in GitHub called “ruleset” whereby the rules can be defined once and then you just have to select which repos they apply
• https://github.blog/changelog/2025-06-16-organization-rulesets-now-available-for-github-team-plans/
• https://github.com/organizations/nf-core/settings/rules
• https://github.com/github/ruleset-recipes
It may be practical for the nf-core pipelines
m
mashehu
05/08/2026, 11:56 AMyep, we have that for the template branch, but I don't like that it is not visible on a repo level where they are applied, so don't want to do
master/maindevm
Matthieu Muffato
05/08/2026, 12:24 PMAh. As admin of my org, I can see all 😁 . Don’t know what developers would see when they go to https://github.com/nf-core/…/settings/rules
m
mashehu
05/08/2026, 12:27 PMoh, somehow the filter for the ruleset was wrong and therefore it didn't apply anything. you should be able to see the org rule here https://github.com/nf-core/rnaseq/settings/rules
mashehu
05/08/2026, 12:29 PMbut the other problem with these is that we have not just pipelines inside our org and the filters are quite limited. probably the easiest would be to add exclusionary custom properties to the non-pipeline repos. but would be great if one could filter based on if the pipeline has a release or based on topics...