Rewrite release workflow #73
Conversation
to maybe-lazily step around the error in this run: https://github.com/solvaholic/octodns-sync/runs/3114434150
and clean up a comment in update-major.yml
to put the release creation logic all in that step, and to intentionally deal with the release branch already existing or not. I feel like this workflow should fail if the release tag already exists. But I'm unsure, so leaving it like this to see how that goes.
and learn, again, to lint locally before committing and pushing.
|
Woohoo! Test run of release.yml made it most of the way through. All the way up to here:
I'll try single-quoting the JSON in the step output, per https://github.saobby.my.eu.orgmunity/t/output-json-string-from-one-action-and-use-it-in-a-workflow-step |
|
Those single-quotes got to the same complaint and exit code 127.
What's that I feel like it really shouldn't be this complicated to send a JSON blob to an API call, so I assume I'm holding it wrong. I'll poke this a bit longer before I cut bait and shop for a 3rd party Action to draft the release. |
in release.yml, to assign step output to $_data.
|
OK, it was just the quotes. Because the expression expands before bash gets a hold of it, wrap the expression in
|
Objectives of these changes are:
733af29 accommodates an excessively long line resulting from where I put credentials for the tag create/push work.
See also #64 and #55