feat: Configure l2geth Docker pipeline to push latest tag #831
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
Thegaram
reviewed
Jun 17, 2024
|
changed it to push latest tag on published releases |
jonastheis
reviewed
Jun 20, 2024
|
I used |
jonastheis
reviewed
Jun 28, 2024
There was a problem hiding this comment.
Should be possible with https://cli.github.com/manual/gh_workflow_run if you add on.workflow_dispatch
gh workflow run docker.yaml --ref push-latest-tag
NazariiDenha
force-pushed
the
push-latest-tag
branch
from
0740008
to
6fb63ce
Compare
|
fixed, now
|
jonastheis
approved these changes
Jul 2, 2024
Thegaram
approved these changes
Jul 3, 2024
|
as explained here "Finally, to have the latest tag set only for the main branch and a release, I disable the default "latest flavor" (which always adds the tag latest) and provide instead the expression" and also from the metadata action docs https://github.com/docker/metadata-action?tab=readme-ov-file#latest-tag |
To trigger it just publish a release on a suitable version |
HAOYUatHZ
pushed a commit
that referenced
this pull request
Jul 31, 2024
* push latest tag * push latest tag on release published * use metadata-action to define tags * test * push ref name on push tag or push latest tag on publishing release
HAOYUatHZ
added a commit
that referenced
this pull request
Jul 31, 2024
* feat: Configure l2geth Docker pipeline to push latest tag (#831) * push latest tag * push latest tag on release published * use metadata-action to define tags * test * push ref name on push tag or push latest tag on publishing release * update --------- Co-authored-by: Nazarii Denha <dengaaa2002@gmail.com>
lwedge99
pushed a commit
to sentioxyz/scroll-geth
that referenced
this pull request
Aug 27, 2024
…h#831) * push latest tag * push latest tag on release published * use metadata-action to define tags * test * push ref name on push tag or push latest tag on publishing release
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.
1. Purpose or design rationale of this PR
Configure l2geth Docker pipeline to push latest tag
#810
2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.gobeen updated?4. Breaking change label
Does this PR have the
breaking-changelabel?