-
Notifications
You must be signed in to change notification settings - Fork 51
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
Branch Ruleset Checks #342
Conversation
… suitable for this project
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 15 out of 22 changed files in this pull request and generated 1 suggestion.
Files not reviewed (7)
- src/main.js: Evaluated as low risk
- src/functions/help.js: Evaluated as low risk
- src/functions/inputs.js: Evaluated as low risk
- README.md: Evaluated as low risk
- action.yml: Evaluated as low risk
- tests/main.test.js: Evaluated as low risk
- tests/functions/help.test.js: Evaluated as low risk
Tip: Copilot code review supports C#, Go, Java, JavaScript, Markdown, Python, Ruby and TypeScript, with more languages coming soon. Learn more
@@ -480,6 +480,16 @@ inputs: | |||
default: | |||
type: string | |||
required: false | |||
use_security_warnings: | |||
description: | |||
type: string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The type for 'description' should be 'boolean' instead of 'string' to match the intended data type.
type: string | |
description: | |
type: boolean |
Copilot is powered by AI, so mistakes are possible. Review output carefully before use.
Just a quick note about this PR it will break deploy bot on private free accounts with a message like:
|
Thanks for your prompt resolution @GrantBirki 🙏🏻 |
Branch Ruleset Checks
This pull request introduces non-blocking safety warnings based off your projects branch rulesets. Rulesets are not to be confused with the classic branch protection settings.
Going forward, you should eventually adopt rulesets over branch protects as they are more robust, implement layering, and can be read via the API without requiring admin rights.
This PR introduces a new
use_security_warnings
setting that defaults totrue
. This setting determines whether this Action should log warning messages related to your ruleset settings. If it discovers potentially dangerous or unsafe configurations, it will be loud and warn you about them. If you don't want these warnings, you may disable them withuse_security_warnings: false
.If you leave these warnings on, notice them in your logs, and want to resolve them, you can also do so by viewing the documentation around these warnings here.
Example 📸
This example shows a potential misconfiguration or security issue. The project has a ruleset defined for
main
that requires pull requests but the total PR reviews required is set to0
. This could potentially be an issue as someone could deploy a pull request that has not been approved by other members.📚 References: