From the course: Coding Exercises: GitHub
Unlock this course with a free trial
Join today to access over 24,700 courses taught by industry experts.
Fix a committed password - GitHub Tutorial
From the course: Coding Exercises: GitHub
Fix a committed password
(8-bit game sounds) - Occasionally, you may end up pushing a commit or a file that has some sensitive information, like a password or an API key. Now you don't want to destroy your entire history, but make a more surgical change. Assuming you've submitted a file with a password and then done some other commits. How do you make sure that GitHub doesn't store those passwords in its history? I'll give you a couple of seconds to pause the video, and think about how you may solve this. (8-bit game sounds) All right, there's a few ways to do this. And in the last video I showed you how to delete the entire history of a project. For this one, we need to be more surgical and I'm going to use a regular git to take care of it. Here's a project where I've done a series of commits. And if I add the commits option here at the end, you can see that I did a first commit. Then I added my extremely sensitive authentication file. And…
Contents
-
-
-
Clone a repo with an empty history2m 28s
-
(Locked)
How do you merge a linear history?4m 22s
-
(Locked)
Add an issue directly from the Terminal2m 56s
-
(Locked)
Deleting all commit history1m 56s
-
(Locked)
Fix a committed password4m 32s
-
(Locked)
Create a monorepo3m 18s
-
(Locked)
Update certain branches3m 18s
-
(Locked)
Process all branches3m 48s
-
(Locked)
Run accessibility audit on push6m 43s
-
(Locked)
Use hidden secrets in projects5m 29s
-
(Locked)
Run actions on a schedule3m 13s
-
(Locked)
Create a Docker container action5m 25s
-
(Locked)
Build and deploy your sites3m 55s
-