Expand linting GitHub Actions Workflow to include oldstable, unstable container images
#74
Comments
atc0005
added a commit
that referenced
this issue
Feb 5, 2022
xpand linting, switch to GHCR Use the same matrix of containers for linting in the `Validate Codebase` GHAW that we're already using for testing and building jobs. This applies the minimum linting requirements in addition to testing "unstable" linting options that may become the new baseline in the future. One notable difference is that out of the matrix of containers used for linting we mark the unstable container as "experimental" and configure the job to ignore linting errors generated by that container. This effectively makes any linting output from the unstable container informational only as intended. SWITCH DOCKER IMAGE SOURCE Switch out images from Docker Hub to Git Hub Container Registry (GHCR). REFERENCES - GH-74 - GH-75
atc0005
added a commit
that referenced
this issue
Feb 5, 2022
EXPAND LINTING TO USE UNSTABLE & OLDSTABLE CONTAINERS Use the same matrix of containers for linting in the `Validate Codebase` GHAW that we're already using for testing and building jobs. This applies the minimum linting requirements in addition to testing "unstable" linting options that may become the new baseline in the future. One notable difference is that out of the matrix of containers used for linting we mark the unstable container as "experimental" and configurecontainer. This effectively makes any linting output from the unstable the job to ignore linting errors generated by that container informational only as intended. SWITCH DOCKER IMAGE SOURCE Switch out images from Docker Hub to Git Hub Container Registry (GHCR). REFERENCES - GH-74 - GH-75
atc0005
added a commit
that referenced
this issue
Feb 5, 2022
EXPAND LINTING TO USE UNSTABLE & OLDSTABLE CONTAINERS Use the same matrix of containers for linting in the `Validate Codebase` GHAW that we're already using for testing and building jobs. This applies the minimum linting requirements in addition to testing "unstable" linting options that may become the new baseline in the future. One notable difference is that out of the matrix of containers used for linting we mark the unstable container as "experimental" and configure the job to ignore linting errors generated by that container. This effectively makes any linting output from the unstable container informational only as intended. SWITCH DOCKER IMAGE SOURCE Switch out images from Docker Hub to Git Hub Container Registry (GHCR). REFERENCES - GH-74 - GH-75
atc0005
added a commit
that referenced
this issue
Feb 5, 2022
EXPAND LINTING TO USE UNSTABLE & OLDSTABLE CONTAINERS Use the same matrix of containers for linting in the `Validate Codebase` GHAW that we're already using for testing and building jobs. This applies the minimum linting requirements in addition to testing "unstable" linting options that may become the new baseline in the future. One notable difference is that out of the matrix of containers used for linting we mark the unstable container as "experimental" and configure the job to ignore linting errors generated by that container. This effectively makes any linting output from the unstable container informational only as intended. SWITCH DOCKER IMAGE SOURCE Switch out images from Docker Hub to Git Hub Container Registry (GHCR). REFERENCES - GH-74 - GH-75
Repository owner
moved this from Todo
to Done
in Update GitHub Actions Workflows to use GHCR, use oldstable, unstable images for linting
Feb 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See atc0005/send2teams#206 for details.
The text was updated successfully, but these errors were encountered: