You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 thePublish 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.
The text was updated successfully, but these errors were encountered: