To try to reduce some of the workflow confusion that PR #69 caused, this PR assumes that maintainers will use bump2version to make a release tag and adds a .bumpversion.cfg file that enables committing changes and tagging the commit with the new version tag (equivalent of adding --commit and --tag at the CLI API).
This PR also adds instructions to walk a maintainer through a release process.
@marceloprates I've left this PR in draft status and have it with parent of 77b992e rather than the current project HEAD so that I can rebase it after whatever actions you take RE: our discussion in https://github.com/marceloprates/prettymaps/pull/69#issuecomment-936460764. I'm of course happy to elaborate or revise any part of this PR! :+1:
To try to reduce some of the workflow confusion that PR #69 caused, this PR assumes that maintainers will use
bump2versionto make a release tag and adds a.bumpversion.cfgfile that enables committing changes and tagging the commit with the new version tag (equivalent of adding--commitand--tagat the CLI API).This PR also adds instructions to walk a maintainer through a release process.
@marceloprates I've left this PR in draft status and have it with parent of 77b992e rather than the current project HEAD so that I can rebase it after whatever actions you take RE: our discussion in https://github.com/marceloprates/prettymaps/pull/69#issuecomment-936460764. I'm of course happy to elaborate or revise any part of this PR! :+1: