# GitHub "Beman Leads" label is up!

**URL:** https://discourse.bemanproject.org/t/github-beman-leads-label-is-up/282
**Category:** Beman Project Development
**Created:** [December 5, 2024, 10:22am UTC](https://discourse.bemanproject.org/t/github-beman-leads-label-is-up/282 "2024-12-05T10:22:15Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![neatudarius](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/neatudarius/32/70_2.png) [@neatudarius](https://discourse.bemanproject.org/u/neatudarius)
#### Post date: [December 5, 2024, 10:22am UTC](https://discourse.bemanproject.org/t/github-beman-leads-label-is-up/282/1 "2024-12-05T10:22:15Z")

</div>

Hello,

I configured the GitHub org to propagate `Beman Leads` label in all repos (as stated in [https://github.com/bemanproject/beman/blob/main/docs/BEMAN\_STANDARD.md#changing-this-document](https://github.com/bemanproject/beman/blob/main/docs/BEMAN_STANDARD.md#changing-this-document)).

Notes:

- It works by design for new repos!  
Here is a PoC  
 ![image](https://canada1.discourse-cdn.com/flex029/uploads/boost/original/1X/24630663d6ee9b24bc0c65103a74fb2473ca5c45.png)
- I had to manually add labels for existing repos…

TLDR: It should work now for all repos in the Beman org!  
Members please use [@project-leads](https://discourse.bemanproject.org/groups/project-leads) (Beman Leads) on Discourse and @Beman Leads label on GitHub if you really need Leads input (e.g., updates in Beman Standard etc)

---

<div class="post-metadata">

### Author: ![river](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/river/32/119_2.png) [@river](https://discourse.bemanproject.org/u/river)
#### Post date: [December 5, 2024, 10:31pm UTC](https://discourse.bemanproject.org/t/github-beman-leads-label-is-up/282/2 "2024-12-05T22:31:25Z")

</div>

I would recommand adding a @ leads team to the GitHub org.

You can add a “team” under the org setting and name it leads, then @ leads would also work on GitHub iirc. We can simplify codeowner file if this is added.

See: [Sign in to GitHub · GitHub](https://github.com/orgs/bemanproject/teams)  
[Creating a team - GitHub Docs](https://docs.github.com/en/organizations/organizing-members-into-teams/creating-a-team)

---

<div class="post-metadata">

### Author: ![dsankel](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/dsankel/32/5_2.png) [@dsankel](https://discourse.bemanproject.org/u/dsankel)
#### Post date: [December 6, 2024, 1:16am UTC](https://discourse.bemanproject.org/t/github-beman-leads-label-is-up/282/3 "2024-12-06T01:16:55Z")

</div>

> [@river](#):
>
> I would recommand adding a @ leads team to the GitHub org.

Good idea. I just did this.

---

<div class="post-metadata">

### Author: ![neatudarius](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/neatudarius/32/70_2.png) [@neatudarius](https://discourse.bemanproject.org/u/neatudarius)
#### Post date: [December 6, 2024, 6:24am UTC](https://discourse.bemanproject.org/t/github-beman-leads-label-is-up/282/5 "2024-12-06T06:24:03Z")

</div>

Should we also add other teams?

E.g. admin  
E.g. codeowners

?

---

<div class="post-metadata">

### Author: ![bretbrownjr](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/bretbrownjr/32/43_2.png) [@bretbrownjr](https://discourse.bemanproject.org/u/bretbrownjr)
#### Post date: [December 9, 2024, 2:09pm UTC](https://discourse.bemanproject.org/t/github-beman-leads-label-is-up/282/6 "2024-12-09T14:09:29Z")

</div>

I vote to keep it simple until we can’t bear the simple thing anymore. If we find the “beman leads” label isn’t helpful for “admin” or “codeowners” things, we can adjust as needed.