Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/felipementel/skills-change-commit-history

My copy of the skills course on changing commit history
https://github.com/felipementel/skills-change-commit-history

Last synced: 28 days ago
JSON representation

My copy of the skills course on changing commit history

Host: GitHub
URL: https://github.com/felipementel/skills-change-commit-history
Owner: felipementel
License: mit
Created: 2024-11-12T23:21:30.000Z (about 1 month ago)
Default Branch: main
Last Pushed: 2024-11-12T23:41:04.000Z (about 1 month ago)
Last Synced: 2024-11-13T00:22:17.920Z (about 1 month ago)
Size: 4.88 KB
Stars: 0
Watchers: 1
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

README

# Remove commit history

Accidental commits can be tricky to remove with Git. In this GitHub Skills course, you'll use BFG Repo-Cleaner to change the history of a Git repository. You can apply what you learn in this course to fully remove sensitive material from your own repository.

## Step 1: Removing sensitive data

_Welcome to "Change commit history"! :wave:_

We'll start by working with `.env` files. These files usually contain sensitive content. For this course, we'll work on removing that file and all traces in the Git history. The first step is to remove the file from repository. We'll alter the history later.

We'll assume you're using the command line, but you can complete the course using your preferred tooling.

**What is _sensitive content_?** Sensitive content is anything that is checked into your repository history that may put you or your organization at risk. This content usually comes in the form of credentials (i.e., passwords, access keys). The best practice for accidentally exposed sensitive content is to invalidate it (i.e., revoke a personal access token), completely remove it from all repository copies, and take measures to prevent future exposure.

See [Deleting a file on GitHub Docs](https://docs.github.com/en/repositories/working-with-files/managing-files/deleting-files-in-a-repository#deleting-a-file) if you need additional help removing a file.

### :keyboard: Activity: Remove `.env` in the project root directory

1. Open your terminal of choice, clone this repository, and switch to your repository directory.
```shell
git clone
cd
```
2. Delete `.env` from the root directory.
```shell
git rm .env
```
3. Commit the removal of `.env`.
```shell
git commit -m "remove .env file"
```
4. Push the removal to GitHub:
```shell
git push
```
5. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.

---

Get help: [Post in our discussion board](https://github.com/orgs/skills/discussions/categories/change-commit-history) • [Review the GitHub status page](https://www.githubstatus.com/)