OvertureMaps / OvertureMaps/workflows
feat: label issues from non-org-members across all repos
@lowlydba is already working on this.
Since Sep 11, 2026.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- Avg merge
- 22h 55m
- Merged PRs (30d)
- 13
Description
Right now there's no way to tell at a glance whether an issue came from an org member or an external contributor across all Overture repos. Triage has to check each author manually.
Add a scheduled, org-wide job that labels newly opened issues from non-org-members. A per-repo issues: opened trigger doesn't cover repos it isn't added to, so this needs a batch job searching the org and checking membership per author, similar to how sync-project-status.yml handles cross-repo ProjectV2 work.
Needs a dedicated GitHub App (org Members: read, repo Issues: write) installed org-wide, plus the usual omf-github-terraform OIDC role/secret wiring.
Contributor guide
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.
Assessment
This issue has not been assessed yet.