Open jamesmunns opened 2 weeks ago
Option 4: Construct the all
team as the union of the team manifests in CI. Optionally check to ensure that this matches the [[github]]
manifest.
Or is the [[github]]
manifest already this?
@BartMassey looking at the toml docs: https://github.com/rust-lang/team/blob/master/docs/toml-schema.md
It appears we could instead:
people.members
of wg-embeded.toml
people.included-teams
section, listing all substeams[[github]]
section as proposed aboveWe should also add website.zulip-stream
while we are at it.
We have a team, "all", that is not managed by the rust-lang teams bots.
All other teams have a toml that has a section like this:
If we want the bot to manage the team access for the "all" account, I think we either need to:
wg-embedded-all.toml
manifest to therust-lang-team/teams
folder: https://github.com/rust-lang/team/tree/master/teams[[github]]
metadata to thewg-embedded.toml
manifest, treating it as the source for the "all" team.all
team, as it's manually maintained atmCC @therealprof, who I THINK set this all up originally. I'm not familiar enough with teams automation to know which option is right, but this came up with thejpster retiring.