-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
📖 Add v1.6 Release Team members' GitHub/Slack handles #9087
📖 Add v1.6 Release Team members' GitHub/Slack handles #9087
Conversation
/cc @vincepri @sbueringer @CecileRobertMichon PTAL |
@furkatgofurov7: GitHub didn't allow me to request PR reviews from the following users: PTAL. Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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/test-infra repository. |
Just one nit otherwise lgtm /assign @vincepri |
655969e
to
e457207
Compare
Thx! /lgtm |
LGTM label has been added. Git tree hash: 1a7876669b25425c84050a61f2894286c5fcb15b
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/check cla |
/check-cla |
It has already cla label but EasyCLA looks to be stuck for some unknown reason.. perhaps I need to force push? |
e457207
to
63529c9
Compare
You can ignore it. We have this across multiple repos and I noticed that the action doesn't block Tide from merging |
/test pull-cluster-api-build-main |
It is still not letting it in 🤷🏼♂️ /retest |
Hm yeah. Can you commit --amend & push --force? Not sure what's going on with the merge pool |
Signed-off-by: Furkat Gofurov <furkat.gofurov@suse.com>
63529c9
to
1179994
Compare
I already did, but force pushed it again now, let's see. Looks like a prow issue to me |
/retest-required |
/check-cla |
The strange thing is: "Tide in merge pool". I merged several PRs today where the GitHub action was pending, that was not an issue (btw there is the upstream issue for that: communitybridge/easycla#4071) |
But looking at the Prow UI. I don't see a merge pool for CAPI including this PR. Can you reopen this PR? (close this one and create a new separate one) |
/easycla |
Interesting. Looks like this blocked it still somehow |
so this was the trick? sorry missed your comments. Thanks anyways for help! |
I didn't think that would help to be honest. Not sure what exactly was going on. I was able to merge PRs in other repos which were in the exact same state. The only thing different here was the "Tide in merge pool" thing. But at this stage CLA shouldn't block afaik. I just retriggered the cla as they mentioned on communitybridge/easycla#4071 that they fixed the CLA issue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/area release
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #