Skip to content
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

Minor fixes for SC election 2023 #1453

Merged
merged 2 commits into from
Oct 17, 2023
Merged

Conversation

ReToCode
Copy link
Member

@ReToCode ReToCode commented Oct 17, 2023

Changes

/kind cleanup

/assign @knative/steering-committee

@knative-prow knative-prow bot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Oct 17, 2023
@knative-prow knative-prow bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 17, 2023
@knative-prow knative-prow bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 17, 2023
@@ -28,7 +28,7 @@ jobs:
name: Verify Deps and Codegen
strategy:
matrix:
go-version: [1.18.x]
go-version: [1.21.x]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like maybe something you accidentally included in the PR? If you remove the change to this file, I can merge the PR with the changes to the elections files.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though, not relevant to the PR without it the GH-actions are broken and the PR will not pass CI checks (https://github.com/knative/community/actions/runs/6542752164). I could do that PR separately, but as we'd like to proceed with the announcement I think we also can keep it in one. WDYT?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aha, I see the reason now. However, we'll need someone from the @knative/technical-oversight-committee to merge this one, since they are the OWNERS for the .github dir. Maybe @dsimansk, since it looks like maybe David is in a European time zone :)

LGTM from an election standpoint.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, done.

@dsimansk
Copy link
Contributor

/approve
/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2023
@knative-prow
Copy link

knative-prow bot commented Oct 17, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dsimansk, ReToCode

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 17, 2023
@knative-prow knative-prow bot merged commit 901ca07 into knative:main Oct 17, 2023
3 checks passed
@csantanapr
Copy link
Member

Thank you for the PR @ReToCode 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants