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 corresponding change in prs.md #110

Merged
merged 2 commits into from
Jun 11, 2019

Conversation

guineveresaenger
Copy link

Fixes instructions to require non-OWNERS entries to open the initial PRs.
/assign @jberkus
/sig contributor-experience

@k8s-ci-robot k8s-ci-robot added the sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. label Dec 5, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guineveresaenger

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

@k8s-ci-robot k8s-ci-robot requested a review from jberkus December 5, 2018 00:22
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 5, 2018
exercises/prs.md Outdated
@@ -10,7 +10,7 @@ See [issues.md](issues.md) for how to prepare for this exercise. If that prep h

This exercise requires working knowledge of creating Github pull requests. If any students at the table have never done this before, their neighbors should help them.

1. Two students at the table (3 for 10-person tables) who have the status "reviewer" should each create a PR. Check the Owners file for status.
1. Two students at the table (3 for 10-person tables) who are NOT in the OWNERS file as Reviewer or Approver should each create a PR. Check the Owners file for status.

Choose a reason for hiding this comment

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

We have OWNERS file in the root dir and separate OWNERS files for each KubeCon. It'd be good to make it clear which OWNERS file the students should check.

Choose a reason for hiding this comment

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

"Check the Owners file ..." s/Owners/OWNERS

Copy link
Author

Choose a reason for hiding this comment

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

That makes sense - added some clarity.

@markjacksonfishing
Copy link
Contributor

/assign @Smirl

@k8s-ci-robot
Copy link
Contributor

@markyjackson-taulia: GitHub didn't allow me to assign the following users: smirl.

Note that only kubernetes-sigs members and repo collaborators can be assigned.
For more information please see the contributor guide

In response to this:

/assign @Smirl

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.

@guineveresaenger
Copy link
Author

@xiangpengzhao - PTAL ❤️

@xiangpengzhao
Copy link

Sorry for late reply :)
/lgtm
👍 💯

@k8s-ci-robot
Copy link
Contributor

@xiangpengzhao: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

Sorry for late reply :)
/lgtm
👍 💯

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.

@xiangpengzhao
Copy link

/cc @jberkus
for LGTM :)

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 28, 2019
@tpepper
Copy link
Member

tpepper commented Jun 11, 2019

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 11, 2019
@k8s-ci-robot k8s-ci-robot merged commit 943db30 into kubernetes-sigs:master Jun 11, 2019
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants