Skip to content

Commit

Permalink
Clarification for update mechanism #2
Browse files Browse the repository at this point in the history
  • Loading branch information
Lineflyer authored Jan 8, 2020
1 parent 001bdb0 commit 61ab718
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,4 +6,4 @@ Script for Mozilla Firefox and Google Chrome browser to [send geocaches directly

Changes must be done on the `master` branch. Once the changes are validated and ready to release, they can be merged to the `release` branch. The script version number needs to be raised after that merge to roll it out.

The script download link on the [c:geo homepage](http://cgeo.org) as well as the update mechanism for the installed script directly targets the raw script on the `release` branch, which means after merging the changes to `release` users will see the update on the website and script hosts (e.g. Greasemonkey) will detect and notify users to update.
The script download link on the [c:geo homepage](http://cgeo.org) as well as the update mechanism for the installed script directly targets the raw script on the `release` branch, which means after merging the changes to `release`, together with the required version number increase, users will see the update on the website and script hosts (e.g. Greasemonkey) will detect and notify users to update.

0 comments on commit 61ab718

Please sign in to comment.