-
Notifications
You must be signed in to change notification settings - Fork 37
Publishing a new version to all current users
Adam Hodges edited this page Feb 28, 2014
·
1 revision
Our userscripts, bookmarklet, and console script are now all pointing at http://jpgohlke.github.io/twitch-chat-filter/chat_filter.user.js
Having the live script hosted on our GitHub page has a few advantages:
- The GitHub page code is housed in a separate branch,
gh-pages
. This means our production code is separate from our working branch, which may not be 100% tested and complete. - Using release tags provides this same benefit, but has the following disadvantages:
- The only way to ensure users are using the latest release is to use the GitHub JSON api to poll for the latest version tag, and to use that to generate a link to the latest code. A little messy, even when using jQuery.
- IE does not like it when you include scripts from raw.github.com, since github strips the MIME type from them.
- GitHub pages provides the latest version with a single static link, and serves our Javascript with the correct MIME type.
PLEASE TEST CODE THOROUGHLY. THESE CHANGES WILL BE PUSHED OUT TO EVERY USER OF OUR SCRIPT!
- Increment the version number in the userscript header. ex:
// @version 1.6
- Commit this change to the
master
branch, and switch over to thegh-pages
branch. - Click on 'Pull Request'.
- The comparison branch names both default to
gh-pages
. Click 'Edit', leavebase: gh-pages
but changecompare:
tomaster
. - Here it would be nice for you to note some of the major changes since the last public release. The commit history should help you with this.
- Click 'Send pull request'.
- Now all that needs to be done is a final review of the changes, and then the pull request can be automatically merged and pushed out to everyone!