lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Doc: CG: Add guideline for use of 'CSS' prefix in commit messages (issue


From: paulwmorris
Subject: Doc: CG: Add guideline for use of 'CSS' prefix in commit messages (issue 325970043 by address@hidden)
Date: Tue, 04 Jul 2017 12:28:12 -0700

Reviewers: ,

Message:
Please review.  Working on css changes for docs, I realized it wasn't
clear to me, from reading the CG, whether the commit prefix should be
'Doc:' or 'Web:' or something else. So this clarifies things.

-Paul

Description:
Doc: CG: Add guideline for use of 'CSS' prefix in commit messages

Please review this at https://codereview.appspot.com/325970043/

Affected files (+5, -0 lines):
  M Documentation/contributor/source-code.itexi


Index: Documentation/contributor/source-code.itexi
diff --git a/Documentation/contributor/source-code.itexi b/Documentation/contributor/source-code.itexi index bfebb9a0c8cf0850a58b62d88d1528af5f0b9eaf..74071217f8c5bcc06dd869c75fb509c35680fd75 100644
--- a/Documentation/contributor/source-code.itexi
+++ b/Documentation/contributor/source-code.itexi
@@ -1252,6 +1252,11 @@ website should use @qq{Web:@tie{}} for English, and
 @address@hidden:@tie{}} for other languages.

 @item
+CSS: Commits that change CSS files should use @qq{Doc:@tie{}CSS:@tie{}},
address@hidden:@tie{}CSS:@tie{}}, or @qq{CSS:@tie{}} depending on whether they
+affect the website, the documentation/manuals, or both.
+
address@hidden
 Changes to a single file are often prefixed with the name of the file
 involved.
 @end itemize





reply via email to

[Prev in Thread] Current Thread [Next in Thread]