Closed alexfornuto closed 3 years ago
P.S. You can see an example of the action here, and the releases here. Note that the release notes include all the commits on the first run, and reset the versioning to 0.0.1, but subsequent releases only included changes past that. Furthermore, after editing the first automatic release version to match the existing convention, the next version updated accordingly.
This PR will create a new patch-level release of Minnaker on subsequent pushes to
master
, using the GitHub Release On Push Action.This PR will not itself create a new release, because of the
norelease
label. We can create additional labels to further customize the behavior of the action, per the action's READMENote: Due to a hard-coded naming convention in the Action (discussed here), this will change the naming convention to include a "v" in the tag on future releases. Manual release procedures should be updated to conform to this convention, if acceptable.
EDIT: Since there are already updates in
master
that aren't in the latest release, consider removing thenorelease
label from this PR to update our current release.