Skip to content

Update 5-finalize-release.md #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .github/steps/5-finalize-release.md
Original file line number Diff line number Diff line change
Expand Up @@ -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. <br>
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)

Expand Down