While using releasenotes extension, we will be using admonitions in commit messages.
The check (-c) flag will look for an admonition within the message. If it exists, it will
verify if it is stated under default or custom admonition. The check fails if the
admonition is not present in any of them. It also suggests similar admonitions
in case the admonition is invalid.
Details
- Reviewers
- durin42 - krbullock 
- Group Reviewers
- hg-reviewers 
- Commits
- rHG6a49c74b1e8f: releasenotes: add check flag for use of admonitions and its validity
Diff Detail
- Repository
- rHG Mercurial
- Lint
- Lint Skipped 
- Unit
- Unit Tests Skipped 
Event Timeline
A style nit, generally +1 and if you get the style nits handled we should be good to go.
| hgext/releasenotes.py | ||
|---|---|---|
| 266 | nit: in a "-quoted string, you can omit \ on ' not a nit: use ("foo"
 "bar")instead of \ to wrap a multi-line string literal (the concatenation is implicit at module load time). | |
Did you add "Differential Revision: https://phab.mercurial-scm.org/D368" to the first line of your commit message? Could you try moving it to the last line?
Sorry I just edited the revision string. Will that work? Or should I update it again with "Differential Revision: https://phab.mercurial-scm.org/D368" at the end.
No worries. The title is good now. "Edit Revision" from the web page works. The title can also be updated by "phabsend", which updates the title to be consistent with the commit message.
@rishabhmadan96 Sorry for jumping late, can you followup with a patch adding some docs for the flag. Also document the behavior of hg releasenotes -c and it will be great if you can add a test for this.
nit: in a "-quoted string, you can omit \ on '
not a nit: use
("foo" "bar")instead of \ to wrap a multi-line string literal (the concatenation is implicit at module load time).