You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/release-pull-request-template.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,14 @@
1
1
-[x] Branch: Starting from `develop`, create a release branch named `release/X.Y.Z` for your changes.
2
2
-[ ] Version bump: Bump the version number in `distributor.php`, `package-lock.json`, `package.json`, `readme.txt` and `tests/php/bootstrap.php` if it does not already reflect the version being released. In `distributor.php` update both the plugin "Version:" property and the plugin `DT_VERSION` constant.
3
-
-[ ] New files: Ensure any new files, especially in the vendor folder, are correctly included in `webpack.config.release.js`.
4
3
-[ ] Changelog: Add/update the changelog in `CHANGELOG.md`.
5
4
-[ ] Props: Update `CREDITS.md` file with any new contributors, confirm maintainers are accurate.
6
5
-[ ] Readme updates: Make any other readme changes as necessary. `README.md` is geared toward GitHub and `readme.txt` contains WordPress.org-specific content. The two are slightly different.
6
+
-[ ] New files: Ensure any new files, especially in the vendor folder, are correctly included in `webpack.config.release.js`.
7
7
-[ ] Since tag updates: ensure `@since` tags indicate the new version, replacing `x.x.x`, `n.e.x.t` and other placeholders.
8
-
-[ ] Merge: Make a non-fast-forward merge from your release branch to `develop` (or merge the Pull Request), then do the same for `develop` into `trunk` (`git checkout trunk && git merge --no-ff develop`). `trunk` contains the stable development version.
8
+
-[ ] Merge: Make a non-fast-forward merge from your release branch to `develop` (or merge the Pull Request), then do the same for `develop` into `trunk` (`git checkout develop && git pull origin develop && git checkout trunk && git pull origin trunk && git merge --no-ff develop`). `trunk` contains the stable development version.
9
+
-[ ] Push: Push your trunk branch to GitHub (e.g. `git push origin trunk`).
10
+
-[ ][Compare](https://github.com/10up/distributor/compare/trunk...develop)`trunk` to `develop` to ensure no additional changes were missed.
9
11
-[ ] Build: Wait for the [Build Stable Release Action](https://github.com/10up/distributor/actions?query=workflow%3A%22Build+Stable+Release%22) to finish running.
10
-
-[ ] Update this pull request's status from `draft` to `ready to merge`.
11
12
-[ ] Review: Do a review of the commit to the `stable` branch to ensure the contents of the diffs are as expected.
12
13
-[ ] Test: Check out the `stable` branch and test it locally to ensure everything works as expected. It is recommended that you rename the existing `distributor` directory and check out `stable` fresh because switching branches does not delete files. This can be done with `git clone --single-branch --branch stable git@github.com:10up/distributor.git`
13
14
-[ ] Either perform a regression testing utilizing the available [Critical Flows](https://10up.github.io/Open-Source-Best-Practices/testing/#critical-flows) and Test Cases or if [end-to-end tests](https://10up.github.io/Open-Source-Best-Practices/testing/#e2e-testing) cover a significant portion of those Critical Flows then run e2e tests. Only proceed if everything tests successfully.
0 commit comments