Migrate branch-push tests from CircleCI to GitHub Actions - #269
Closed
conservationtimothy wants to merge 1 commit into
Closed
Migrate branch-push tests from CircleCI to GitHub Actions#269conservationtimothy wants to merge 1 commit into
conservationtimothy wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Goal
Run the gc-scripts-hub unit tests in GitHub Actions whenever a branch is pushed.
Screenshots
Not applicable.
What I changed and why
I replaced the CircleCI test configuration with a GitHub Actions workflow triggered by pushes to any branch. The workflow preserves the existing Ubuntu 24.04, Python 3.11.10, PostgreSQL, tox, tox-docker, dependency cooldown, and Docker gateway configuration.
I also updated the contribution guidance to identify GitHub Actions as the repository’s CI system.
How I convinced myself this is right
By comparing the new workflow with the previous CircleCI job step by step.
What I'm not doing here
LLM use disclosure
None