community, org: generate yaml with list of users access levels #3500
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
|
Skipping CI for Draft Pull Request. |
kubevirt-bot
added
do-not-merge/work-in-progress
dhiller
force-pushed
the
check-repo-and-team-org-access
branch
from
3c78c89 to
008ce84
Compare
|
See also kubevirt/community#239 |
dhiller
force-pushed
the
check-repo-and-team-org-access
branch
from
008ce84 to
5c53877
Compare
dhiller
changed the title
Adds a tool robots/cmd/org-access-check that generates a yaml document
with the access levels all the users have per a repository.
The yaml is structured like this:
```yaml
{access-level}:
{repository}:
- {user1}
- ...
where access level is (admin|write|maintain)
See explanations on repository roles here [1]
[1]: https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#repository-roles-for-organizations
Signed-off-by: Daniel Hiller <[email protected]>
dhiller
force-pushed
the
check-repo-and-team-org-access
branch
from
5c53877 to
064ef5a
Compare
kubevirt-bot
removed
the
do-not-merge/work-in-progress
Will actually output three yaml files, looking from different angles: * accessPermissions To Repositories To Collaborators * repositories To AccessPermissions To Collaborators * collaborators To AccessPermissions To Repositories Signed-off-by: Daniel Hiller <[email protected]>
dhiller
force-pushed
the
check-repo-and-team-org-access
branch
from
064ef5a to
d1b9230
Compare
|
/uncc @aglitke @tiraboschi |
|
/approve Self overriding since there's no impact |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dhiller 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 |
kubevirt-bot
added
the
approved
dhiller
added
lgtm
chandramerla
pushed a commit
to chandramerla/project-infra
that referenced
this pull request
Aug 26, 2024
…irt#3500) * community, org: generate yaml with list of users access levels Adds a tool robots/cmd/org-access-check that generates a yaml document with the access levels all the users have per a repository. The yaml is structured like this: ```yaml {access-level}: {repository}: - {user1} - ... where access level is (admin|write|maintain) See explanations on repository roles here [1] [1]: https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#repository-roles-for-organizations Signed-off-by: Daniel Hiller <[email protected]> * community, access: output yaml files with access Will actually output three yaml files, looking from different angles: * accessPermissions To Repositories To Collaborators * repositories To AccessPermissions To Collaborators * collaborators To AccessPermissions To Repositories Signed-off-by: Daniel Hiller <[email protected]> --------- Signed-off-by: Daniel Hiller <[email protected]>
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.
What this PR does / why we need it:
Adds a tool
robots/cmd/org-access-checkthat generates three yamldocuments with the access levels all the users have per a repository.
Each of the yaml files will enable looking from a different angle:
The first yaml is basically structured like this:
where access level is (admin|write|maintain)
Others are structured likewise.
See explanations on repository roles here 1
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.
Release note: