-
Notifications
You must be signed in to change notification settings - Fork 11
Added the feedback form and after merge workflow #119
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
Conversation
Signed-off-by: antedotee <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
|
@clubanderson Please have a look. |
|
@antedotee why are you trying to merge this to kubestellar:main when this is a2a? @MAVRICK-1 why are all these CI things failing? |
|
@clubanderson majority are lint issues. Needed some reconfiguration but . Application is working file . Will release the binaries for cli soon |
|
Oops, didnt check. Sorry. |
@clubanderson, On hovering over the link, and also checking the route, it opened the main branch on a2a. Also, other merged PRs are also looking the same(i.e. looks like it is merging into ks/main while it really is merging into a2a/main) |
Signed-off-by: antedotee <[email protected]>
|
@MAVRICK-1 can you look at the CI issues here |
|
@antedotee Can you show us if the workflow works in your repo ?? if you have tested it ? |
I have copied this over from other repo, so it will work. Still, I will check again once in my fork. |
|
/ok-to-test |
|
@antedotee: The following tests failed, say
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. |

same as title