Security Policy violation Branch Protection

[ghost]

This issue was automatically created by Allstar.

Security Policy Violation
No protection found for branch master

---

Issue created by GSA Allstar. See remediation hints in the README.

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

[aj-stein-gsa]

I need to investigate this because given all the protections we have I am not sure why this Allstar report is indicating the branch isn't protected, perhaps GItHub Rulesets are not currently supported (as opposed to the OG branch protection rules; the former is new to me).

[allstar-gsa]

Updating issue after ping interval. See its status below.

---

No protection found for branch master

[aj-stein-gsa]

@nateprice18f, I see that you are a frequent committer to the controlling GSA/.allstar repository. Can you confirm if the Allstar checks and rules as configured can detect the new Rulesets feature, not just branch protections? We use the former not the latter and they are more robust and specific. It seems Allstar does not understand this configuration.

If possible, I am happy to work with you and others in your team, if there are others that are maintainers I must coordinate with, if such a new or changed rule is supported. I dabble, but a lot of these GH features are new (oh do, I know 😆).