-
Notifications
You must be signed in to change notification settings - Fork 677
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
Support for the "same" team across different orgs #2559
Comments
Is this with |
yeah |
/sig contributor-experience Somewhat implied by this would be the idea that org membership should be cross-org as well. Unclear whether it would be better to have a "global" overlay, or treating one org as a source of truth to be mirrored (ref: #966) |
the Xzibit strategy? 😄 (I put a tool around your tool to make a new tool) I agree with the "make the tool too clever" thing--the though part is where to draw the line... We already assume GitHub, so it seems like we should have the same limitations/constraints as GitHub, acknowledging that they will change (we have already been "bitten" by their change to protected branches that match a given regex stepping on our branches protected via regex pattern). I do like your idea of generating the config though... 🤔 |
/area github-management |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
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. |
/reopen I'm going to move this to kubernetes/org, if there are technical implementation details that need to find their way into this repo, we can discuss on followup issues or PRs |
@spiffxp: Reopened this issue. In response to this:
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. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/lifecycle frozen |
/priority awaiting-more-evidence |
/remove-priority important-longterm |
What would you like to be added:
In GitHub (at least GitHub Enterprise),
Teams
cannot be cross-org. I would like to support cross-org "Teams".Why is this needed:
To "get around" the problem, we just replicate the same teams across different orgs. It would be nice to reference a
Team
, with liketeamRef
or something, that is specified at theOrgs
level so they can be reused.The text was updated successfully, but these errors were encountered: