[WIP] api: prevent unverified users from starting builds #1040
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
kleesc
force-pushed
the
prevent-unverified-user-from-building
branch
7 times, most recently
from
c81e8cb
to
dc637cc
Compare
Requires a user to be verified in order to be able to start build of a repository. TODO: By default, organization aren't verified. This means that as part of this change, in addition to newly created orgs, existing orgs would need to be verified. Which means sending new confirmation emails for each.
kleesc
force-pushed
the
prevent-unverified-user-from-building
branch
from
dc637cc
to
d98b5ec
Compare
|
@kleesc: PR needs rebase. 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Requires a user to be verified in order to be able to start build of a
repository.
TODO: By default, organization aren't verified. This means that as
part of this change, in addition to newly created orgs, existing orgs
would need to be verified. Which means sending new confirmation emails
for each.