-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add Greasy Fork integration #74
base: main
Are you sure you want to change the base?
Conversation
Sorry I have no idea why the CI fails and what build-pipeline does… I notice that it also fails in #72, so I guess it's not my fault? |
if not project_info.homepage: | ||
project_info.homepage = greasy_fork_info.url | ||
|
||
if ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here metadata on GitHub takes precedence. This behaviour is the same as other integrations.
Question: Should Greasy Fork take precedence?
Some people maintain multiple scripts in a single repo, but all script can live in only one repo. Therefore, metadata on Greasy Fork might be more specific (and more suitable) than those on GitHub.
What kind of change does this PR introduce?
Description:
Greasy Fork is a site for user scripts. This PR adds integration for
greasy_fork_id
.Greasy Fork provides their data in a simple and straight forward
greasyfork.org/scripts/*.json
(e.g. https://greasyfork.org/scripts/1.json) and no token is required.(I've been using it for a few months, and it always works.)
Checklist: