Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cli tool #2

Open
mafintosh opened this issue May 9, 2015 · 8 comments
Open

cli tool #2

mafintosh opened this issue May 9, 2015 · 8 comments

Comments

@mafintosh
Copy link

i was just looking for something exactly like this! i need to use it from the command line though. would be cool if this supported command line usage 👍

@bcomnes
Copy link
Collaborator

bcomnes commented May 9, 2015

Via gh-release

@bcomnes
Copy link
Collaborator

bcomnes commented May 9, 2015

@paulcpederson
Copy link
Collaborator

@mafintosh yes, meant to be used via gh-release. Although I guess I could write a quick cli for it to do just this component. That's a pretty good idea!

@paulcpederson
Copy link
Collaborator

Just to make sure, you mean you want to upload something to an existing release without creating a new release, right?

@maneetgoyal
Copy link

Will be nice to have 👍. If the CLI comes with regex support for those asset paths, it will be a nice addition as well. Also, suggest that the CLI can read the GitHub token from some environment variable to prevent hardcoding the token anywhere in the release script.

Here's some info on my use-case:

  • I am using Lerna to manage a monorepo.
  • Lerna provides CLI support to publish new releases/tags on GitHub.
  • But it is lacking the support to release the assets alongside making a new release.
  • Once a new release is made, Lerna updates its lerna.json file with the latest version number.
  • Hoping that this version number could be used to figure out the upload_url.
  • Using that URL, I wish to upload some assets.

Will start trying out using the current gh-release-assets API to do it in the meantime.

@bcomnes
Copy link
Collaborator

bcomnes commented Oct 20, 2020

Only existing solution I can think of would be to use shell expansion and join the results with commas. Otherwise adding glob expressions to gh-release's assets flag would be the best way to do this I imagine. This wouldn't be too hard, but low priority personally so I will unlike work on that any time soon. I would consider a PR.

@bcomnes
Copy link
Collaborator

bcomnes commented Oct 20, 2020

You may also consider using a github action:

https://github.com/actions/upload-release-asset

But that is actions specific.

@maneetgoyal
Copy link

Thanks for the suggestion @bcomnes. I was able to work with the current programmatic API to upload the assets. (Used octokit/rest to get the upload_url corresponding to a given tag/version-number). It works fine so the CLI support is a low priority for me too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants