From the course: Git for Teams

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Keeping secrets

Keeping secrets - Git Tutorial

From the course: Git for Teams

Start my 1-month free trial Buy for my team

Keeping secrets

“

- [Instructor] Git is great for sharing code with your team, but it's one of the worst places to store secrets, like passwords, API keys, or certificates. If your team uses Git to store secrets, it's kind of like you're hiding your house key under the doormat. It's convenient, but it's not very secure. Here's why. There are many ways that others can gain access to your code. Some of that access might be intentional. Maybe your organization wants to promote collaboration so they make the repositories of different teams available for others in the company to view, or maybe you're working on an open source project. My point here is that there's reasons you might want to share your code, but if your repository contains secrets, you either can't share the code or you're going to be sharing all of your system's secrets, and that's not a good thing. Even if your Git repository isn't shared outside of your team, it's still…

Contents