-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Official repo version behind / no PR for current version #176
Comments
obviously not a bug, can't seem to unassign label -- apologies |
Just created an issue in the GOG API repo (closest thing I could see to where it would be applicable): gogcom/galaxy-integrations-python-api#194 in case that helps. |
Hi, thanks for raising the problem.
I think the issue is caused by auto-disabling github actions after 60days of no activity: https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow Issue on gog side is a good idea. |
That's a great point. I overlooked that possibility. |
Describe the bug
In other community integrations, the "official" FriendsOfGalaxy repo seems to use a bot to identify when a PR is needed, and creates one when it sees the version has been updated. (See for example https://github.com/FriendsOfGalaxy/galaxy-integration-uplay/pulls and https://github.com/FriendsOfGalaxy/galaxy-integration-rockstar/pulls) Now, GOG doesn't necessarily seem to be actually processing those PRs since January, but for some reason the Humble plugin doesn't even have a PR in the queue for its updates. (https://github.com/FriendsOfGalaxy/galaxy-integration-humble/pulls) I am guessing the bot wasn't clever enough to realize 10 > 9 (aka string or digit compare vs numerical), but that's not your problem of course :) However, you could probably do the PR manually and then... well, it could sit there waiting like the other community integrations, I guess, but at least that's another step forward!
Expected behavior
All handled downstream (don't we all wish!)
Plugin installed
directly from Galaxy / manually from your repository releases
Provide logs
n/a
The text was updated successfully, but these errors were encountered: