jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[ci skip] correctly explain how to use [backport] tags

Browse source
This commit is contained in:
narimiran 2021-05-12 13:57:43 +02:00
commit 60b4fa71a8
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/contributing.rst
View file

@ -453,9 +453,9 @@ General commit rules
1. Important, critical bugfixes that have a tiny chance of breaking 1. Important, critical bugfixes that have a tiny chance of breaking
somebody's code should be backported to the latest stable release somebody's code should be backported to the latest stable release
branch (currently 1.4.x) and maybe also all the way back to the 1.0.x branch. branch (currently 1.4.x) and maybe also all the way back to the 1.0.x branch.
The commit message should contain the tag ``[backport]`` for "backport to all The commit message should contain the tag ``[backport]`` for "backport to the latest
stable releases" and the tag ``[backport:$VERSION]`` for backporting to the stable release" and the tag ``[backport:$VERSION]`` for backporting back to the
given $VERSION. given $VERSION (and all newer releases).
2. If you introduce changes which affect backward compatibility, 2. If you introduce changes which affect backward compatibility,
make breaking changes, or have PR which is tagged as ``[feature]``, make breaking changes, or have PR which is tagged as ``[feature]``,