Skip to content
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

add links and pluralize Merge-Commit #420

Closed
wants to merge 1 commit into from
Closed
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
8 changes: 5 additions & 3 deletions source/de/1.0.0/index.html.haml
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,8 @@ version: 1.0.0
- vandamme = "https://github.com/tech-angels/vandamme/"
- iso = "http://www.iso.org/iso/home/standards/iso8601.htm"
- ghr = "https://help.github.com/articles/creating-releases/"
- gnustyle = "https://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#Style-of-Change-Logs"
- gnunews = "https://www.gnu.org/prep/standards/html_node/NEWS-File.html#NEWS-File"

.header
.title
Expand Down Expand Up @@ -135,7 +137,7 @@ version: 1.0.0

%p
Commit-Logs in einem Changelog sind eine schlechte Idee: Sie beinhalten lauter
überflüssige Dinge, wie Merge-Commit, Commits mit schlechten Bezeichnungen,
überflüssige Dinge, wie Merge-Commits, Commits mit schlechten Bezeichnungen,
Änderungen an der Dokumentation, etc.

%p
Expand Down Expand Up @@ -192,8 +194,8 @@ version: 1.0.0
Gibt es ein standardisiertes Changelog-Format?

%p
Leider nicht. Es gibt zwar den GNU Changelog Styleguide oder den
zwei Absätze langen GNU NEWS-Datei "Leitfaden". Beide sind aber
Leider nicht. Es gibt zwar den #{link_to "GNU Changelog Styleguide", gnustyle} oder den
#{link_to "zwei Absätze langen GNU NEWS-Datei", gnunews} "Leitfaden". Beide sind aber
unzureichend.

%p
Expand Down