Figure out automation of the "all" team on GH

Open
#768 3 comments 0 reactions 0 assignees View on GitHub

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.

Screenshot 2024-06-19 at 10 33 24

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.toml manifest to the rust-lang-team/teams folder: https://github.com/rust-lang/team/tree/master/teams
  • Add the [[github]] metadata to the wg-embedded.toml manifest, treating it as the source for the "all" team.
  • Get rid of the all team, 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-embedded/wg

All issues in rust-embedded/wg

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.