-
Notifications
You must be signed in to change notification settings - Fork 871
feat: Add file path protection to rulesets #2415
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
Conversation
|
I have tested the changes on an account with paid features so this is now good for review. |
|
@kfcampbell would it be possible to get feedback on this PR please. |
|
|
||
| * `tag_name_pattern` - (Optional) (Block List, Max: 1) Parameters to be used for the tag_name_pattern rule. This rule only applies to repositories within an enterprise, it cannot be applied to repositories owned by individuals or regular organizations. Conflicts with `branch_name_pattern` as it only applied to rulesets with target `tag`. (see [below for nested schema](#rules.tag_name_pattern)) | ||
|
|
||
| * `file_path_restriction` -(Optional) (Block List, Max 1) Parameters to be used for the file_path_restriction rule. When enabled restricts access to files within the repository. (See [Below for nested schema](#rules.file_path_restriction)) |
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.
| * `file_path_restriction` -(Optional) (Block List, Max 1) Parameters to be used for the file_path_restriction rule. When enabled restricts access to files within the repository. (See [Below for nested schema](#rules.file_path_restriction)) | |
| * `file_path_restriction` - (Optional) (Block List, Max 1) Parameters to be used for the file_path_restriction rule. When enabled restricts access to files within the repository. (See [Below for nested schema](#rules.file_path_restriction)) |
|
@grahamhar you might want to rebase as you have conflicts due to the GitHub SDK having been bumped to the next major version. |
Thanks for
Thanks for the review @stevehipwell I think everything is addressed now. |
|
@nickfloyd or @kfcampbell sorry for the direct tag. Is it possible to get a review of this PR? |
|
Any update here? ❤️ Looking for this 🚀 |
|
Also checking in, need this functionality on our team, thank you. |
|
any update in this feature |
|
Yeah would be awesome to finally get this. |
|
any updates on this feature ? |
|
Any update on this? |
|
I'm not a maintainer, but FYI I noticed that this line isn't updated with |
Thanks for the eyes @bmurphey-latacora updated the missing ref |
|
Is there any update on this feature? The Github SDK allows to configure push restrictions since v66 which has been a part of this provider since end of October 2024. It's a vital security feature to prevent users from pushing to sensitive file paths like .github . Are there any plans to push this forward? |
| * `file_path_restriction` - (Optional) (Block List, Max 1) Parameters to be used for the file_path_restriction rule. When enabled restricts access to files within the repository. (See [below for nested schema](#rules.file_path_restriction)) | ||
|
|
||
| * `max_file_size` - (Optional) (Block List, Max 1) Parameters to be used for the max_file_size rule. When enabled restricts the maximum size of a file that can be pushed to the repository. (See [below for nested schema](#rules.max_file_size)) | ||
|
|
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.
It looks like the docs are missing for file_extension_restriction here?
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.
I just added them. I believe an example is missing as well.
|
Any updates on this? |
Co-authored-by: Steve Hipwell <[email protected]>
Co-authored-by: Steve Hipwell <[email protected]>
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.
LGTM
Resolves #2371
Here is the doc that shows the push type rules are restricted.
Before the change?
After the change?
Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!