🏗️ - Amended ci workflow to run on pushes to main - #46
Open
swmcc wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
poke :) |
Contributor
Author
|
Is this repo still active. If you want I can be a maintainer if there are issues? |
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
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.
Introduced a refinement to our
.github/workflows/python-tests.ymlCI workflow file. Specifically, it amends the trigger conditions to include direct push events to themainbranch. This adjustment ensures that any code changes pushed directly tomain, whether through merge operations or direct commits, are subject to our new tests.The amended
ontrigger section now explicitly lists:Expected Impact:
mainwill now trigger our testing suite, catching potential issues before they affect our production environment.