Repository navigation
ci: enforce the package proxy guard - #11
Merged
Merged
Conversation
ExtraToast
added
type: chore
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.
Makes this repository enforce the package proxy.
.github/workflows/repository-hygiene.yml, callingrepository-hygiene-guard.ymlwithpackage-proxy-guard: enforceand passingPACKAGES_PROXY_TOKEN.8b5462a).require-package-proxy: trueon installing shared workflows and setup steps that pass the token (1 added).Guard findings: 0 before, 0 after, so enforce is on.
Checks: actionlint reports nothing new on the changed workflows; the guard run locally reports 0 findings. Dockerfiles and docker build steps are untouched.
Refs JorisJonkers-dev/workspace#167