summaryrefslogtreecommitdiffstats
path: root/doc/developer-guide/commit-guidelines.md
diff options
context:
space:
mode:
authorkshithijiyer <kshithij.ki@gmail.com>2019-09-02 18:43:36 +0530
committerAmar Tumballi <amarts@gmail.com>2019-09-05 04:55:30 +0000
commitb0dbe11556c17ba6ea0b7d85b741bd4807c81c9c (patch)
tree35b58d0fc52d28bb24f1215509a7a8fa485546c2 /doc/developer-guide/commit-guidelines.md
parent724c657995a2e148243eeb78c68b620c6d7714a5 (diff)
[Doc] Fixing 404 links in markdown files.
Problem: While running markdown-link-checker it was observed that there were a large number of 404 links present in the documentation present in the form of markdown files in the project. This was casued due to the following reasons: 1. Repos being removed. 2. Typo in markdown links. 3. Restructring of directoires. Solution: Fixing all the 404 links present in the project. fixes: bz#1746810 Change-Id: I30de745f848fca2e9c92eb7493f74738f0890ed9 Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
Diffstat (limited to 'doc/developer-guide/commit-guidelines.md')
-rw-r--r--doc/developer-guide/commit-guidelines.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/developer-guide/commit-guidelines.md b/doc/developer-guide/commit-guidelines.md
index 9b191dac178..38bbe525cbd 100644
--- a/doc/developer-guide/commit-guidelines.md
+++ b/doc/developer-guide/commit-guidelines.md
@@ -118,7 +118,7 @@ The 'bug' line can reference a bug in a few ways. Gerrit creates a link to the b
**Updates: bz#1193929** -- use 'Updates: bz#NNNN' if the commit is only a partial fix and more work is needed.
**Updates: #175** -- use 'Updates: #NNNN' if the commit is only a partial fix and more work is needed for the feature completion.
-We encourage the use of Co-Authored-By: name <name@example.com> in commit messages to indicate people who worked on a particular patch. It's a convention for recognizing multiple authors, and our projects would encourage the stats tools to observe it when collecting statistics.
+We encourage the use of `Co-Authored-By: name <name@example.com>` in commit messages to indicate people who worked on a particular patch. It's a convention for recognizing multiple authors, and our projects would encourage the stats tools to observe it when collecting statistics.
### Summary of Git commit message structure