Update removing-sensitive-data-from-a-repository.md

[diberry]

Add gitleaks as another way to prevent secrets leaks.

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md	fpt ghec ghes@ 3.12 3.11 3.10 3.9 3.8	fpt ghec ghes@ 3.12 3.11 3.10 3.9 3.8

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[nguyenalex836]

@diberry Thanks so much for opening a PR! I'll get this triaged for review ✨

[jc-clark]

Thanks for the suggestion to add a preventative measure to this list @diberry!

After checking in with our team, we agreed that this information is good to include here, but we can't document the third-party gitleaks tool. I suggested changes for enabling push protections for the repository instead.

What do you think? If you commit the changes, I can help merge.

docs updated as per @jc-clark's suggestion

[mchammer01]

This LGTM

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡