This repository was archived by the owner on Oct 15, 2025. It is now read-only.
Conversation
The current `build.yml` runs on pushes to all branches, including the `gh-pages` branch which only contains the docs and no actual code, and will therefore always fail CI. It makes more sense to run it only on the "main" branches (`master` and `develop`), especially given the resources consumed by the CI runs.
Contributor
Author
|
I also updated the CI workflow names so they're not just all called "Python" - this will make debugging easier if things break on specific python/gdal versions. |
mcgarth
approved these changes
Apr 11, 2022
Contributor
mcgarth
left a comment
There was a problem hiding this comment.
Changes make sense. @adu461386118 to confirm and merge
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The current
build.ymlruns on pushes to all branches, including thegh-pagesbranch which only contains the docs and no actual code, and will therefore always fail CI. It makes more sense to run it only on the "main" branches (masteranddevelop), especially given the resources consumed by the CI runs.