فهرست منبع

Merge pull request #10149 from tetrapod00/cherrypick-docs

Clarify cherry-picking workflow in Contributing to the Documentation
Max Hilbrunner 9 ماه پیش
والد
کامیت
4c6763707b
1فایلهای تغییر یافته به همراه5 افزوده شده و 3 حذف شده
  1. 5 3
      contributing/documentation/contributing_to_the_documentation.rst

+ 5 - 3
contributing/documentation/contributing_to_the_documentation.rst

@@ -49,9 +49,11 @@ contribute, you should also read:
 Contributing changes
 --------------------
 
-**Pull Requests should use the** ``master`` **branch by default.** Only make Pull
-Requests against other branches (e.g. ``2.1`` or ``3.0``) if your changes only
-apply to that specific version of Godot.
+**Pull requests should use the** ``master`` **branch by default.** Only make pull
+requests against other branches (e.g. ``3.6`` or ``4.2``) if your changes only
+apply to that specific version of Godot. After a pull request is merged into
+``master``, it will usually be cherry-picked into the current stable branch by
+documentation maintainers.
 
 Though less convenient to edit than a wiki, this Git repository is where we
 write the documentation. Having direct access to the source files in a revision