-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
k8s content image: Image from PR should not be tagged latest
#11643
k8s content image: Image from PR should not be tagged latest
#11643
Conversation
Add tag flavors input as false. The images built from a PR are not to receive the latest tag.
Output in the comment what commit was used to build the image.
Code Climate has analyzed commit 4293530 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 59.8% (0.0% change). View more on Code Climate. |
🤖 A k8s content image for this PR is available at: Click here to see how to deploy itIf you alread have Compliance Operator deployed: Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and: |
The |
I think @Vincent056 is working on something to fix the deployment using |
@Vincent056 It seems that the |
Description:
latest
. Set action metadata inputflavor latest=false
Rationale:
latest
tag should be used on images built from merged changes.latest
tag is assigned to the same image that has a PR number tag (This won't be noticeable if a PR was merged and no PR was updated after that).Review Hints: