Skip to content

Commit

Permalink
Remove commit release notes branch step
Browse files Browse the repository at this point in the history
1. We don't push to upstream at this point
2. Committing changes before opening a PR is an obvious step, I think.
  • Loading branch information
jdavcs committed Mar 25, 2024
1 parent 630a473 commit 9408893
Showing 1 changed file with 0 additions and 3 deletions.
3 changes: 0 additions & 3 deletions galaxy_release_util/bootstrap_history.py
Original file line number Diff line number Diff line change
Expand Up @@ -276,9 +276,6 @@
- [ ] Open newly created files and manually curate major topics and release notes.
- [ ] Run ``python scripts/release-diff.py release_${previous_version}`` and add configuration changes to release notes.
- [ ] Add new release to doc/source/releases/index.rst
- [ ] Commit release notes.
git add docs/; git commit -m "Release notes for $version"; git push upstream ${version}_release_notes
- [ ] Open a pull request for the release notes branch.
- [ ] Merge release note pull request.
Expand Down

0 comments on commit 9408893

Please sign in to comment.