-
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃尡 Added go directive test #10261
馃尡 Added go directive test #10261
Conversation
af9a60d
to
7db691a
Compare
/retest |
thanks for picking up this task! |
7db691a
to
009e9c5
Compare
009e9c5
to
be30ac3
Compare
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.
Otherwise lgtm
be30ac3
to
21c399a
Compare
/retest |
@sbueringer am not sure if my changes are breaking stuff could you confirm |
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.
One nit, otherwise lgtm
/test pull-cluster-api-test-main This seems a flake (there is also a discussion thread in slack) |
21c399a
to
4f81786
Compare
/area ci |
@AvineshTripathi thanks for working on this! |
LGTM label has been added. Git tree hash: fe36be89b3c3b477151bc76d50197697b088c8ed
|
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.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: killianmuldoon 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 |
/lgtm /hold cancel |
Would be great if we can manual cherry-pick this PR into 1.6 & 1.5 (in both cases we should use 1.20 as GO_DIRECTIVE_VERSION) @AvineshTripathi Do you want to take this over? |
Hey sure I can take those up, can you explain bit more "manual cherry-pick this pr into.." |
Basically you create the same PR against the release-1.6 & release-1.5 branch (but using 1.20 as GO_DIRECTIVE_VERSION). You can either do it entirely manually or something like this: git checkout release-1.6
git checkout -b release-1.6-go-directive
git cherry-pick <commit of this PR>
# Change GO_DIRECTIVE_VERSION to 1.20
git commit --amend
... Just saying "Manually" because usually we have a cherry-pick bot. But this won't be enough as we want to use 1.20 |
fixes #10258