-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create a Guide/Template: Preventing Secrets & Credentials Leaks in GitHub #69
Comments
@salice
|
When I published the Lucky Parking secrets, I got the warning within minutes and fixed it right away, which included killing the old credentials and creating new ones. |
@gregpawin how long did the clean up take? https://github.com/hackforla/engineering/issues/17#issuecomment-891511226 |
It took less than 30 mins |
sophias repo with pre commit hooks |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Prior version of issue
OverviewWe need to create a guide to preventing secrets and credentials from being published on GitHub. Action Items
ResourcesUpdate tracker issue (TBD) with the name of item you are working Projects with no mention of "secrets" and/or "credentials" in their Contributing.md or README.md file:
Projects to check |
Overview
We need to create a guide to preventing secrets and credentials from being published on GitHub.
Action Items
The phases in the guide-making process are listed below. Each phase displayed in blue is linked to a wiki page with instructions on how to complete that phase. Open the wiki page in a new tab, copy the instructions for each part into the section labeled 'Tasks' at the bottom of this issue, and complete each task listed.
Resources
Projects with no mention of "secrets" and/or "credentials" in their Contributing.md or README.md file:
Projects to check
Tasks
The text was updated successfully, but these errors were encountered: