community
community copied to clipboard
Add SIG docs: New Contributors Meet and Greet
Adds the SIG docs: New Contributors Meet and Greet events as suggested by @sftim
The committers listed above are authorized under a signed CLA.
- :white_check_mark: login: Rishit-dagli / name: Rishit Dagli (3707a3720e8b0c9eb95a07ab5851dda6354281ff)
Welcome @Rishit-dagli!
It looks like this is your first PR to kubernetes/community 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes/community has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @Rishit-dagli. Thanks for your PR.
I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
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/test-infra repository.
Thanks!
/ok-to-test
Ah, missed this. Thanks for pointing this out!
/retest
The merge conflicts are now fixed!
To complete the pull request process, please assign nikhita after the PR has been reviewed.
/assign @nikhita
@reylejano https://github.com/kubernetes/community/pull/6679/commits/627aed33d22320445abe265f7c688ed64e334883 and https://github.com/kubernetes/community/pull/6679/commits/379fbe3c227a4f5e87bf4273c374eb2a1e8e42ee address your reviews
/unassign
Please reassign back to me when this has LGTM from SIG Docs leads. Thanks!
/lgtm lgtm's from 2 SIG Docs co-chairs (myself and Divya) and 1 SIG Docs tech lead (Tim) /assign @nikhita
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mrbobbytables, Rishit-dagli
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [mrbobbytables]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment