Skip to content
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

feat: enable secret protection #52

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SamMorrowDrums
Copy link
Collaborator

Enable checking of repository settings, and add a specific tool for toggling secret scanning settings only.

Screencast.From.2025-03-30.01-30-15.mp4

Advanced Security is a pre-requisite for using this on private repos (and or Secret Protection SKU when it launches next week), so we will need to handle those quirks.

I had to make some manual http calls, because the go wrapper does not wrap this feature.

TODO before merge:

  • decide on cleanest way to handle the public/private repo stuff where there is a pre-requisite to enabling secret protection
  • we could just have a catch-all configuration setting endpoint, with the massive number of possible settings?
  • I can make all fields optional, but the annoying thing is that you can't have push protection on, without secret protection. The API is not conducive to wrapping neatly in a tool, but I must find a way.
  • can we also enable Code Scanning default setup?
  • add tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant