OvertureMaps / OvertureMaps/workflows

feat: label issues from non-org-members across all repos

Open
#103 0 comments 0 reactions 1 assignee View on GitHub

@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

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.