Add GitHub Actions workflow to verify Docker Hub secrets#382
Closed
maany wants to merge 1 commit intorucio:masterfrom
Closed
Add GitHub Actions workflow to verify Docker Hub secrets#382maany wants to merge 1 commit intorucio:masterfrom
maany wants to merge 1 commit intorucio:masterfrom
Conversation
Member
Author
|
Closing as this will not be further debugged. The issue was fixed by resetting the org secrets! |
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.
This pull request introduces a new GitHub Actions workflow to verify the presence and length of Docker Hub secrets. The most important change is the addition of the
test-secrets.ymlfile, which ensures that the necessary secrets are set correctly before proceeding with the workflow.New GitHub Actions workflow:
.github/workflows/test-secrets.yml: Added a workflow namedorg-secretsthat runs on pull requests and manual triggers. It includes steps to verify thatDOCKER_HUB_USERNAMEandDOCKER_HUB_ACCESS_TOKENsecrets are set and have non-zero length.