-
Notifications
You must be signed in to change notification settings - Fork 36
Check teams from branch PRs #313
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
base: main
Are you sure you want to change the base?
Conversation
|
Ok, I think we are getting closer to something functional here. Summary of features:
Pending work:
I know this is going to be a nightmare to review, so I suggest merging a good baseline we are happy with, and adjusting the files in several PRs little by little until the CI passes. Especially if we need to update team composition and other metadata in Github (for bookkeeping). |
|
This is amazing @jaimergp! I agree that getting this merged as a baseline that then we can update overtime is a great strategy. |
|
Posting the pre-commit logs here because they don't fit in pre-commit.ci: |
|
I don't agree with merging snapshots of the progress here as a baseline, since that has the smell of not taking governance information seriously, and I don't want to end up in legal debates later about why we merged this. That said, if you need a break from this, or frankly if you don't have the access needed because of the org ownership situation, I'm happy to devote time to carry this over the finish line with the items you wrote above. I'm happy to devote time to it this week. |
I have time and energy for this, but I don't have permissions to do any cleanups in the
I don't have strong opinions on how we proceed, but some counterpoints:
|
|
Oh, and I also need help reviewing the types of teams. Not clear how some of them were created and with which mission. |
|
…olds the GH teams representing the governance team.
|
FYI, I just renamed the |
|
We will also need to rename the Zulip channel: #builds-tools |
Description