-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Ephemeral patchbot on GH Actions #33253
Labels
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:5
Is this really necessary? It's running one ci tool in another one. I would say its more flexible to convert the patchbot steps into github workflows, as we have already done with the linter and #33263. This should replace the patchbots completely in the long term. |
comment:6
Replying to @tobiasdiez:
GH Actions is not a CI, it runs CIs |
This comment has been minimized.
This comment has been minimized.
comment:10
Completed, can be closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PR sagemath/sage-patchbot#155 adds a GH Actions workflow to sage-patchbot, which runs the patchbot in a Docker container using one of the pre-built images that our CI pushes to https://github.com/orgs/sagemath/packages?repo_name=sage
Follow-ups:
.github/workflows/run_patchbot.yml: Actually handle github.event.inputs.patchbot_ticket sage-patchbot#156 (fixup)
.github/workflows/run_patchbot_cygwin.yml: New sage-patchbot#157 (Cygwin)
Run as a scheduled workflow on GH Actions. Users who fork the GitHub repo can activate the workflow by depositing a repository secret
SAGE_PATCHBOT_ENVS
of the formubuntu-focal-standard ubuntu-hirsute-standard ...
. The workflow would create 1 job per platform listed thereCC: @fchapoton
Component: scripts
Issue created by migration from https://trac.sagemath.org/ticket/33253
The text was updated successfully, but these errors were encountered: