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

Releases should be tagged #40

Open
Download opened this issue Nov 3, 2015 · 0 comments
Open

Releases should be tagged #40

Download opened this issue Nov 3, 2015 · 0 comments

Comments

@Download
Copy link

Download commented Nov 3, 2015

I see you don't tag your releases. That's unfortunate because it makes it harder to use your plugin directly from RawGit CDN.

If you were to tag your releases we could use the Branch dropdown at the top of the page to select a release, then paste the URL to the .js file for that release into RawGit and use it from there. But because no releases are tagged, we have to use a specific commit now.

Tagging a release is simple and costs only a few minutes. Use the releases tab. You as owner of the repo will see a button there marked Draft a new release. Press it, fill in a version tag, title and optional description and hit the Publish release button. Bam! A new release has been created that gives us all a stable target for including in our page.

Let me know if you would like to know more, I'd be glad to help.

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

No branches or pull requests

1 participant