# and tagging it with a new tag for the release.
# currently needs to be told the new release name, which is actually also gotten from
# the "next_version" script. if these differ, there will be confusion for users about
# and tagging it with a new tag for the release.
# currently needs to be told the new release name, which is actually also gotten from
# the "next_version" script. if these differ, there will be confusion for users about
# + better if we could get the version automatically, but there is a circular dependency where we want to check out the new branch by version number.
# these are the steps i take on feisty meow when i have a dev branch that is
# + better if we could get the version automatically, but there is a circular dependency where we want to check out the new branch by version number.
# these are the steps i take on feisty meow when i have a dev branch that is
# includes adding the tag for the new release and such. there are manual
# steps for adding the commit comments, including an introspection phase
# with gitk before the release commit comment is created.
# includes adding the tag for the new release and such. there are manual
# steps for adding the commit comments, including an introspection phase
# with gitk before the release commit comment is created.
- # commit the full set of changes for the master branch now, including the tags.
-#echo about to commit master branch with all those changes--hit enter
+ # commit the full set of changes for the main branch now, including the tags.
+#echo about to commit main branch with all those changes--hit enter