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.

Sign up for GitHub

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

Jump to bottom

WIP: master: update release-tools + OWNERS #300

Closed
wants to merge 2 commits into from
Closed

WIP: master: update release-tools + OWNERS #300

wants to merge 2 commits into from

Conversation

pohly
Copy link
Contributor

@pohly pohly commented May 21, 2021

Squashed 'release-tools/' changes from ad83def..f325590

f3255906 Merge pull request #149 from pohly/cluster-logs
4b03b308 Merge pull request #155 from pohly/owners
a6453c86 owners: introduce aliases
feb20e26 prow.sh: collect cluster logs

git-subtree-dir: release-tools
git-subtree-split: f325590

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 21, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pohly

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 added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. labels May 21, 2021
@k8s-ci-robot
Copy link
Contributor

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubernetes-csi org. You can then trigger verification by writing /verify-owners in a comment.

  • kubernetes-csi-reviewers
    • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.
  • kubernetes-csi-approvers
    • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.

@pohly pohly closed this May 21, 2021
@pohly pohly deleted the prow-update-master branch May 21, 2021 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@msau42 msau42 Awaiting requested review from msau42

@saad-ali saad-ali Awaiting requested review from saad-ali

Assignees
No one assigned
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. do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@pohly @k8s-ci-robot