Hi - I'm hoping someone can point me towards a "best practice" example on adding binary assets to GitHub releases of a program.
Take https://github.com/myitcv/gobin/releases/tag/v0.0.2 as an example. I have added cross compiled binaries as assets to the v0.0.2 release. What I would now like to do is provide one-liner release instructions to the README for various OS's. One issue with the current approach is that when any of those binaries are downloaded the file is missing the execute permissions. That's easily fixable with chmod.... Or alternatively, I could upload archives instead of the binaries themselves... Indeed I'm sure there are plenty of other approaches. So I'm looking for advice on best practice, best practice that leads to the most sensible one-liner install instructions in READMEs. Any pointers much appreciated. Thanks, Paul -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
