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

Add dorzel to OWNERS as Reviewer #1808

Merged
merged 1 commit into from
Feb 27, 2025

Conversation

adambkaplan
Copy link
Member

Changes

Promote Dylan Orzel (@dorzel) to reviewer in the shipwright-io/build repo, in recognition of his contributions related to scheduling builds on Kubernetes clusters. Many of these implement the API-level features described in SHIP-0039 [1].

Thank you Dylan for your efforts!

[1] https://github.com/shipwright-io/community/blob/main/ships/0039-build-scheduler-opts.md

/kind cleanup

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

Promote Dylan Orzel (@dorzel) to `reviewer` in the shipwright-io/build
repo, in recognition of his contributions related to scheduling builds
on Kubernetes clusters. Many of these implement the API-level features
described in SHIP-0039 [1].

Thank you Dylan for your efforts!

[1] https://github.com/shipwright-io/community/blob/main/ships/0039-build-scheduler-opts.md

Signed-off-by: Adam Kaplan <adam.kaplan@redhat.com>
@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 24, 2025
@openshift-ci openshift-ci bot added release-note-none Label for when a PR does not need a release note kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Feb 24, 2025
@openshift-ci openshift-ci bot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Feb 24, 2025
Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

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

/approve

Copy link
Contributor

openshift-ci bot commented Feb 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 24, 2025
@adambkaplan
Copy link
Member Author

Looks like I got the order backwards - we need to invite the person to the org before adding to the OWNERS file.

Since there were no objections at the community meeting, and this PR has "approve", I have gone ahead and invited @dorzel to the shipwright-io org as a "Build Contributor". Once the invite is accepted we can re-verify the OWNERS file.

@adambkaplan
Copy link
Member Author

/verify-owners

@openshift-ci openshift-ci bot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Feb 26, 2025
Copy link
Contributor

@qu1queee qu1queee left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 27, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 8013e07 into shipwright-io:main Feb 27, 2025
20 checks passed
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. release-note-none Label for when a PR does not need a release note size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants