Anyway, if you need to maintain your own branched versions. You should also replace metadata such as the update/download URL with your own. Avoid automatic updates to the origin branch.

Thanks, that makes sense.

But that’s also where I get entirely befuddled by the various .*URL$ metadata fields’ effects… If I do fork (or copy-paste) into, say, a personal GitHub repo, I can get a URL like https://raw.githubusercontent.com/treyharris/WK-Jitai-webfonts/customMods/jitai.user.js that will follow my customMods branch.

But which .*URL$ field(s) would I reset to reflect? All of them?

Like in this case, the only one currently included is:

https://github.com/treyharris/WK-Jitai-webfonts/blob/e282efe1f407dc7360b7a66e93ea491159c4aef0/jitai.user.js#L9:

// @homepageURL https://gist.github.com/obskyr/9f3c77cf6bf663792c6e

which isn’t a link to the script, but to its (Gist) repo—which contains two files, the JS and a Markdown readme. Would than mean changing this to something like

// @homepageURL https://github.com/treyharris/WK-Jitai-webfonts/tree/customMods

? And/or would I need to introduce new @updateURL and/or @downloadURL lines (which, I assume, would point directly at a raw file like https://raw.githubusercontent.com/treyharris/WK-Jitai-webfonts/customMods/jitai.user.js)?

Will Userscripts support the update of greasy fork's user script? #248

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions