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
Remove executable file permission from OWNERS files #72525
Merged
k8s-ci-robot
merged 1 commit into
kubernetes:master
from
justinsb:owners_should_not_be_executable
Feb 15, 2019
Merged
Remove executable file permission from OWNERS files #72525
k8s-ci-robot
merged 1 commit into
kubernetes:master
from
justinsb:owners_should_not_be_executable
Feb 15, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
release-note-none
Denotes a PR that doesn't merit a release note.
size/XS
Denotes a PR that changes 0-9 lines, ignoring generated files.
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
labels
Jan 3, 2019
k8s-ci-robot
added
area/apiserver
area/kubelet
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
sig/apps
Categorizes an issue or PR as relevant to SIG Apps.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
sig/autoscaling
Categorizes an issue or PR as relevant to SIG Autoscaling.
sig/cluster-lifecycle
Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
sig/network
Categorizes an issue or PR as relevant to SIG Network.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
and removed
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
labels
Jan 3, 2019
justinsb
added
the
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
label
Jan 4, 2019
k8s-ci-robot
removed
the
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
label
Jan 4, 2019
/retest |
/test pull-kubernetes-local-e2e-containerized |
justinsb
force-pushed
the
owners_should_not_be_executable
branch
from
January 12, 2019 00:43
76cd843
to
dd19b92
Compare
/retest |
It is reasonable to change permissions of OWNERS files which are unnecessary to be executable :-) /lgtm |
k8s-ci-robot
added
the
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
label
Jan 25, 2019
/test pull-kubernetes-local-e2e-containerized |
I am in favor of not executing the OWNERS /retest |
k8s-ci-robot
added
the
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
label
Feb 15, 2019
hiddeco
pushed a commit
to hiddeco/kubernetes
that referenced
this pull request
Apr 6, 2020
…e_executable Remove executable file permission from OWNERS files
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.
area/apiserver
area/kubelet
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
release-note-none
Denotes a PR that doesn't merit a release note.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
sig/apps
Categorizes an issue or PR as relevant to SIG Apps.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
sig/autoscaling
Categorizes an issue or PR as relevant to SIG Autoscaling.
sig/cluster-lifecycle
Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
sig/network
Categorizes an issue or PR as relevant to SIG Network.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
size/XS
Denotes a PR that changes 0-9 lines, ignoring generated files.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's actually a number of these, so I'm sending a few PRs grouping them thematically.