Skip to content

Commit

Permalink
Update readme (#498)
Browse files Browse the repository at this point in the history
The main purpose of this PR is to test and investigate build triggers
  • Loading branch information
recrwplay authored Apr 19, 2023
1 parent 1332ffc commit 44e7b1e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -70,4 +70,4 @@ There are a few edge cases where we might want to work only on the current branc
** Open a draft PR against `dev`, with a label for the specific version it is targeting - this can be shared & reviewed in draft mode, but will not be mergeable until it is pointed at the next release.
** Create a feature branch from `dev`, to be merged into `dev` when appropriate.
* When a new version is ready to published, the `5.x` branch will get a git tag, named with the exact version (for example, **5.1.0**), signifying that this point-in-time marks the completion of the work for that minor release.
* The `dev` branch, with all merged content for the next release, will then be merged
* Updates merged into the `dev` branch for the next release are cherry-picked into the `5.x` branch.

0 comments on commit 44e7b1e

Please sign in to comment.