Figure out automation of the "all" team on GH
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github
- Domain
- devops
Research direction
Start by reading the rust-lang/team teams folder and comparing the existing [[github]] entries in the TOML manifests with wg-embedded.toml. Determine how the rust-lang teams bot handles GitHub team access and whether the all team should receive its own manifest, metadata, or removal. Done means the chosen approach is agreed and the all team’s ownership is either automated or explicitly removed.
Written by the indexing model from the issue text.
Description
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:
[[github]]
orgs = ["rust-embedded"]
team-name = "resources"
If we want the bot to manage the team access for the "all" account, I think we either need to:
- add a
wg-embedded-all.tomlmanifest to therust-lang-team/teamsfolder: https://github.com/rust-lang/team/tree/master/teams - Add the
[[github]]metadata to thewg-embedded.tomlmanifest, treating it as the source for the "all" team. - Get rid of the
allteam, as it's manually maintained atm
CC @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.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rust-embedded/wg
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
rust-embedded/wg#923 · 12 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
rust-embedded/wg#910 · 15 comments · 6 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
rust-embedded/wg#893 · 18 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
rust-embedded/wg#884 · 1 comment · 6 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
rust-embedded/wg#870 · 1 comment · 1 reaction ·
All issues in rust-embedded/wg
Similar issues
-
kind/bug Ubuntu 24
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kubernetes-sigs/kubespray#13532 ·
-
Needs Design Priority: Wishlist
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
elementary/flatpak-platform#253 ·
-
tagbot-manual
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100