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 chandramerla as kubevirt org member #3708

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

chandramerla
Copy link
Contributor

GitHub Username

@chandramerla

Requirements

[x] I have reviewed the community code of conduct (https://github.com/kubevirt/kubevirt/blob/master/CODE_OF_CONDUCT.md)

[x] I have enabled 2FA on my GitHub account (https://github.com/settings/security)

[x] I have subscribed to the kubevirt-dev e-mail list (https://groups.google.com/forum/#!forum/kubevirt-dev)

[x] I am actively contributing to KubeVirt

[x] I have two sponsors that meet the sponsor requirements listed in the community membership guidelines

[x] I have spoken to my sponsors ahead of this application and they have agreed to sponsor my application

[x] I have publicly introduced myself to the community through one of the community communication channels

(https://github.com/kubevirt/community#socializing)

Sponsors

List of contributions to the KubeVirt project

PRs reviewed and/or authored

Issues responded to

Important

After this pull request has been merged, an invitation to the KubeVirt GitHub organization will be automatically sent to the new member. The new member needs to accept the invitation to receive member status.

@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Oct 23, 2024
@kubevirt-bot
Copy link
Contributor

Hi @chandramerla. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

Copy link
Member

@brianmcarey brianmcarey left a comment

Choose a reason for hiding this comment

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

Hi @chandramerla - it will be good to have you as part of the org.

Can you update this so that you are added in alphabetical order?

@brianmcarey
Copy link
Member

/test all

@chandramerla
Copy link
Contributor Author

Hi @chandramerla - it will be good to have you as part of the org.

Can you update this so that you are added in alphabetical order?

Thanks, Brian. I've reordered names in the the current list to be sorted alphabetically

Copy link
Contributor

@dhiller dhiller left a comment

Choose a reason for hiding this comment

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

Hey @chandramerla , great to have you here! 🥳

Welcome to the KubeVirt community! 🎉

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2024
@dhiller
Copy link
Contributor

dhiller commented Oct 24, 2024

/approve

/hold for two days so to give others the chance to chime in.

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 24, 2024
@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 24, 2024
Copy link
Member

@brianmcarey brianmcarey left a comment

Choose a reason for hiding this comment

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

/lgtm

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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants