...
create a local back up branch in case the branch is messed up
switch to the branch of the PR that has the sensitive data
make a commit to delete the sensitive data if you have not (this is for the sensitive data not to show on GitHub after force-pushing)
push the branch
rewrite commit history using
git rebase -i
(https://docs.github.com/en/get-started/using-git/using-git-rebase-on-the-command-line )force-push
| Expand | ||
|---|---|---|
| ||
Situation: We have a PR that has two commits. The first commit has sensitive data. 
|
