免费学习该课程!
今天就开通帐号,24,700 门业界名师课程任您挑!
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…
内容
-
-
-
Clone a repo with an empty history2 分钟 28 秒
-
(已锁定)
How do you merge a linear history?4 分钟 22 秒
-
(已锁定)
Add an issue directly from the Terminal2 分钟 56 秒
-
(已锁定)
Deleting all commit history1 分钟 56 秒
-
(已锁定)
Fix a committed password4 分钟 32 秒
-
(已锁定)
Create a monorepo3 分钟 18 秒
-
(已锁定)
Update certain branches3 分钟 18 秒
-
(已锁定)
Process all branches3 分钟 48 秒
-
(已锁定)
Run accessibility audit on push6 分钟 43 秒
-
(已锁定)
Use hidden secrets in projects5 分钟 29 秒
-
(已锁定)
Run actions on a schedule3 分钟 13 秒
-
(已锁定)
Create a Docker container action5 分钟 25 秒
-
(已锁定)
Build and deploy your sites3 分钟 55 秒
-