Комментарии:
commits dont lie... hahahahah
ОтветитьThe Shakira reference caught me off guards.
ОтветитьWhat if I want to keep the file but just replace the secret with an encrypted value?
ОтветитьWell-explained video with clear instructions. I have difficulties using the newest git-filter-repo, and this helps me save much time. Thanks!
ОтветитьGreat video. Will this works for merge request too? The issue we’re running into is that GitLab merge requests are read-only and therefore can’t be updated, so the push to the merge request refs is rejected, meaning secrets persist in the merge requests.
ОтветитьDoes this matter for local-only git repo? If I eventually push it to Github I want to make sure my file is not included in the history (my config file was not in my gitignore initially).
Ответитьthis ruins your PRs because the root of the updated branch differs from the main's root
ОтветитьMy commits don't lie is so bad hahaha.
ОтветитьThis worked for me! Was able to delete my secret keys from my git history. Thanks!
ОтветитьYou are awesome!!!!!! THANK YOU
ОтветитьThank you for this! worked perfectly
ОтветитьThank you. Now I can fix my stupidity.
ОтветитьMan, thank you so much for this video:)
ОтветитьVery well explained. Thank you.
ОтветитьIt is ridiculous of how much effort it takes to do this.
Ответитьhow can i remove an image that i uploaded to github?
Ответитьwhy does it keep telling me bad revision "rm", I double checked the spaces and everything
Ответитьwhy does it keep telling me bad revision "rm", I double checked the spaces and everything.
Ответить