-
Notifications
You must be signed in to change notification settings - Fork 73
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
Remove the redundant token.yaml empty file #768
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ibuziuk, tolusha, vinokurig The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@artaleks9 hello, could you please take a look at the failing tests? |
/retest |
@vinokurig: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
@ibuziuk hello, |
Build 3.20 :: server_3.x/384: Console, Changes, Git Data |
Build 3.20 :: sync-to-downstream_3.x/8836: Console, Changes, Git Data |
Build 3.20 :: push-latest-container-to-quay_3.x/5102: Console, Changes, Git Data |
Build 3.20 :: get-sources-rhpkg-container-build_3.x/8955: server : 3.x :: Build 66805230 : quay.io/devspaces/server-rhel9:3.20-2 |
Build 3.20 :: server_3.x/384: Upstream sync done; /DS_CI/sync-to-downstream_3.x/8836 triggered |
Build 3.20 :: update-digests_3.x/8674: Console, Changes, Git Data |
What does this PR do?
Remove the empty token.yaml file. A leftover has been committed.
Screenshot/screencast of this PR
What issues does this PR fix or reference?
How to test this PR?
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedRelease Notes
Reviewers
Reviewers, please comment how you tested the PR when approving it.