feat: support for latestpushed retention rule#369
Open
shreddedbacon wants to merge 1 commit intomainfrom
Open
Conversation
4 tasks
shreddedbacon
force-pushed
the
harbor-retention-pushed
branch
2 times, most recently
from
eb6d278 to
9de7954
Compare
shreddedbacon
force-pushed
the
harbor-retention-pushed
branch
2 times, most recently
from
2ba571c to
3e25100
Compare
shreddedbacon
force-pushed
the
harbor-retention-pushed
branch
from
3e25100 to
df39145
Compare
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
2 participants
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.
Checklist
See uselagoon/lagoon#4074 for description. This is supporting code changes for
latestPushedretention policies.As this code is only accessed if the message from core contains the information, this should be fine to merge ahead of the changes in core.