Purge a file from history (Challenge)

Introduction

Git is a popular version control system that allows developers to track changes in their codebase. However, sometimes it becomes necessary to completely remove a file from the repository's history. This challenge will guide you through the process of purging a file from Git's history.

Skills Graph

Purge a file from history

Suppose you accidentally committed a file containing sensitive information, such as API keys or passwords, to your Git repository. You realize that this file should never have been committed and want to completely remove it from the repository's history. However, simply deleting the file and committing the change will not remove it from the repository's history. The file will still be accessible in previous commits, which could pose a security risk.

Tasks

To complete this challenge, you will use the Git repository git-playground from your GitHub account, which comes from a fork of https://github.com/labex-labs/git-playground.git. This repository contains a file named file1.txt that should never have been committed.Please purge file1.txt from the repository's history.

1. Clone the repository to your local machine from https://github.com/your-username/git-playground.
2. Navigate to the directory and configure the identity.
3. Delete the file from the repository's index.
4. Rewrite the repository's history, removing all instances of file1.txt.
5. Force push the changes to the remote repository.

After completing these steps, file1.txt will be completely removed from the repository's history and after running git log --remotes, you will not see the commit on file1.txt.

Summary

Purging a file from Git's history is a necessary step when sensitive information has been accidentally committed. This challenge has guided you through the process of purging a file from Git's history using the git filter-branch command. Remember to use caution when rewriting a repository's history, as it can have unintended consequences.