-
-
Notifications
You must be signed in to change notification settings - Fork 1
LOOK RIGHT NOW THERES A SECURITY ALERT #23
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
Comments
This comment has been minimized.
This comment has been minimized.
I closed the alert as not relevant. |
The api key was for firebase, I put it accidentally, I then deleted it. |
How do I hide the commit |
Also revoke the api key |
I'll do it |
This is how - spoiler alert copilot ai generated it Guide to Permanently Removing Files from Git HistoryWhen you need to permanently remove files from your Git history, there are several approaches you can take. This guide covers two popular methods: using BFG Repo-Cleaner and Table of Contents
IntroductionRemoving files from Git history can be necessary for several reasons, such as removing sensitive information (e.g., passwords, API keys) or large files that bloat the repository size. This guide will help you through the process using both BFG Repo-Cleaner and Safety ConsiderationsBefore you begin, it's important to be aware of the following safety considerations:
Using BFG Repo-CleanerBFG Repo-Cleaner is a simpler and faster alternative to Prerequisites
Steps to Remove Files
Using git filter-repo
Prerequisites
Steps to Remove Files
Post-Cleanup StepsAfter running either BFG Repo-Cleaner or
References |
https://github.com/Scratch-Coding-Hut/Scratch-Coding-Hut.github.io/security/secret-scanning/3
secret scanning alert for google api key we need to fix it
The text was updated successfully, but these errors were encountered: