-
Notifications
You must be signed in to change notification settings - Fork 10
Fairly major changes; add --update #4
base: master
Are you sure you want to change the base?
Conversation
Apologies @parsley42, somehow I wasn't watching this repo and this completely slipped my attention! Interesting idea 🤔Would we need both |
Hah! Thanks for getting back with me @lox - I was a little surprised to get a reply on this PR. ;-) Yah, I think I could rename |
(adding) ... It looks like the only place I can use a |
@parsley42 this is a long shot but you're active on github, how do you build this project? I can't find anything in the readme |
@Dominikaaaa happy to help if you need! |
@Dominikaaaa Fairly straightforward (well, for regular Go programmers at least):
Or, if you added
Hope that helps. |
@parsley42 thank you! I've never used go before but I wanted to build the pulls to try them myself. Appreciate it! |
I just want to lead out and say I'm not expecting this to be merged (certainly not as-is), but I wanted to give buildkite a look at my changes, and offer to create a cleaner PR if the changes are desired.
My goal was a github-release tool that allowed smooth updates to snapshot pre-releases. As I push changes to feature branches, it's helpful to have automatic build and publish to a pre-release on github, but none of the existing github release publishing tools appeared to offer that ability. Of the tools I examined, your github-release seemed most amenable to modification.
While my patched version suits my needs, it puts more requirements on potential users, as the commit hash is now required. The big upshot for me is that when e.g. a new 1.0.1-snapshot build completes, github correctly reports the snapshot release was "5 minutes ago", and not "10 days ago" (when the first 1.0.1-snapshot was built).