Migrate PR Builder to GitHub Actions #560
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JackPGreen
force-pushed
the
make-pr-builder
branch
2 times, most recently
from
8e1c82b to
9bc6068
Compare
JackPGreen
force-pushed
the
make-pr-builder
branch
from
65e2fbd to
2d20ec3
Compare
JackPGreen
changed the title
Contributor
Author
ihsandemir
approved these changes
Oct 22, 2025
emreyigit
approved these changes
Oct 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#558 failed the PR builder because it runs on Jenkins, inside a custom Python-3.7 Docker image.
Python 3.7 has been end-of-life for 2 years, and is too old to support the proposed changes.
We could upgrade to a newer Docker image (or even make a new one), but I think it would be easier to migrate to GitHub Actions instead - the runner already includes a recent Python installation.
Changes:
Post-merge actions: