Use DOCKERHUB_TOKEN instead of DOCKER_RELEASE #75
Open
antoinebhs wants to merge 1 commit intomainfrom
Open
Conversation
antoinebhs
changed the title
Signed-off-by: BOUHOURS Antoine <antoine.bouhours@rte-france.com>
antoinebhs
force-pushed
the
rename-docker-release
branch
from
419ff8f to
d08862e
Compare
antoinebhs
changed the title
antoinebhs
changed the title
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
No
What kind of change does this PR introduce?
Consistency with other actions that use DOCKERHUB_TOKEN
What is the current behavior?
manual-dockerdeploy-backend-app-generic.yml use DOCKER_RELEASE
What is the new behavior (if this is a feature change)?
manual-dockerdeploy-backend-app-generic.yml use DOCKERHUB_TOKEN