doc: update docs for tag selection of new release (#20996)
* doc: update docs for tag selection of new release * Fix versioning
This commit is contained in:
@@ -39,10 +39,18 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
|
||||
{% data reusables.repositories.releases %}
|
||||
3. Click **Draft a new release**.
|
||||

|
||||
4. Type a version number for your release. Versions are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging). We recommend naming tags that fit within [semantic versioning](http://semver.org/).
|
||||

|
||||
4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release.
|
||||
{% ifversion fpt %}
|
||||

|
||||
1. Click **Create new tag**.
|
||||

|
||||
{% else %}
|
||||

|
||||
{% endif %}
|
||||
5. Use the drop-down menu to select the branch that contains the project you want to release.
|
||||

|
||||
{% ifversion fpt %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
6. Type a title and description for your release.
|
||||

|
||||
7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
|
||||
|
||||
Reference in New Issue
Block a user