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
In the same field as #318, I have noticed something strange (but it’s not very serious problem).
I pushed a newer version of a script (2015.5.13.1555) then a few minutes later, before Greasy Fork had updated, I pushed another version (2015.5.13.1611).
When Greasy Fork updated on github web hook, it did take the latest script version (1611) code, but its latest commit message was not concatenated in the script changelog :
CHG. added another english article (an) to the loose title ignore list
The text was updated successfully, but these errors were encountered:
Greasy Fork will get the commit messages from the webhook, wait a bit for GH's caching to expire, then get the file contents. If you push again before it grabs the file contents, then it's possible for what happened to you to happen.
Really, I think we should update GF to get the library with git rather than over a (caching) HTTP server. That would prevent this problem and makes things better all-around.
JasonBarnabe
changed the title
A commit message was not concatenated in the script changelog (github webhook)
Use git to get code on webhook request
May 17, 2015
In the same field as #318, I have noticed something strange (but it’s not very serious problem).
I pushed a newer version of a script (
2015.5.13.1555
) then a few minutes later, before Greasy Fork had updated, I pushed another version (2015.5.13.1611
).When Greasy Fork updated on github web hook, it did take the latest script version (
1611
) code, but its latest commit message was not concatenated in the script changelog :The text was updated successfully, but these errors were encountered: