From bf6292ceb9799969bc9a935c3e73f6e2d19fb0ed Mon Sep 17 00:00:00 2001 From: Bryan Wilches <60490258+BryanWV@users.noreply.github.com> Date: Wed, 19 Feb 2025 16:36:45 -0500 Subject: [PATCH] Update 5-finalize-release.md Adding extra information to protect files in a project in step 5 --- .github/steps/5-finalize-release.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/steps/5-finalize-release.md b/.github/steps/5-finalize-release.md index 62fdb39..c3a71b6 100644 --- a/.github/steps/5-finalize-release.md +++ b/.github/steps/5-finalize-release.md @@ -10,7 +10,8 @@ _Awesome work on the release notes :+1:_ ### Finalizing releases -It's important to be aware of the information what will be visible in that release. In the pre-release, the version and commit messages are visible. +It's important to be aware of the information that will be visible in the release. In the pre-release, the version and commit messages are visible. Sensitive files in your project like passwords, encryption keys, Personal Access Tokens (PAT's) or private user files are going to be published if you're not careful enough, leading to a potential misuse of the informatin and unauthorized access and malicious activities.
+If you're interested in this subject the [GitHub Documentation to get started in Git](https://docs.github.com/en/get-started/getting-started-with-git) may be appealing to you. To know more about protecting personal information in your code you can be guided in [.gitignore files](https://docs.github.com/en/get-started/getting-started-with-git/ignoring-files). ![image](https://user-images.githubusercontent.com/13326548/47883578-bdba7780-ddea-11e8-84b8-563e12f02ca6.png)