CI: Compile r.example and v.example #2351
Merged
Conversation
This file contains 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
Compiling the two example C modules was part of the release procedure. This makes it part of the CI. For now the check is (strangely) in the Pylint workflow because it is documentation and that workflow already does a test build of Sphinx (all three need to build from source first). Other places would be a separate doc generating and checking workflow or adding these to GCC checks to ensure higher quality standard.
ninsbl
pushed a commit
to ninsbl/grass
that referenced
this pull request
Oct 26, 2022
Compiling the two example C modules was part of the release procedure. This makes it part of the CI. For now the check is (strangely) in the Pylint workflow because it is documentation and that workflow already does a test build of Sphinx (all three need to build from source first). Other places would be a separate doc generating and checking workflow or adding these to GCC checks to ensure higher quality standard.
ninsbl
pushed a commit
to ninsbl/grass
that referenced
this pull request
Feb 17, 2023
Compiling the two example C modules was part of the release procedure. This makes it part of the CI. For now the check is (strangely) in the Pylint workflow because it is documentation and that workflow already does a test build of Sphinx (all three need to build from source first). Other places would be a separate doc generating and checking workflow or adding these to GCC checks to ensure higher quality standard.
neteler
pushed a commit
to nilason/grass
that referenced
this pull request
Nov 7, 2023
Compiling the two example C modules was part of the release procedure. This makes it part of the CI. For now the check is (strangely) in the Pylint workflow because it is documentation and that workflow already does a test build of Sphinx (all three need to build from source first). Other places would be a separate doc generating and checking workflow or adding these to GCC checks to ensure higher quality standard.
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.
Compiling the two example C modules was part of the release procedure. This makes it part of the CI.
For now the check is (strangely) in the Pylint workflow because it is documentation and that workflow already does a test build of Sphinx (all three need to build from source first). Other places would be a separate doc generating and checking workflow or adding these to GCC checks to ensure higher quality standard.