Open
Conversation
Author
|
Noticed that the triggers: uc-python.github.io/.github/workflows/publish.yml Lines 6 to 11 in 6a7ba91 are causing runs and deployments for PRs going into main, which override the published version from Wondering if we should remove the PR trigger, or find a way to deploy elsewhere. Not a huge deal, as we can always do a manual trigger on |
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.
Got several deprecation notices on previous runs, and the latest run from
mainproduced errors for unsupported actions managed by GitHub, so looking to move to the latest releases for all actions in the workflow.