Issue Details
Description
When a Pull Request (PR) is opened, the system automatically applies the label:
NSOC'26
This helps categorize PRs related to the NSOC 2026 program immediately upon creation.
Why needed
Improves discoverability and filtering for the maintainers and reviewers.
Enables program-level dashboards, metrics, and easier tracking.
Ensures consistent labeling without relying on contributors to remember it.
Makes review workflows (reviewers, priorities, boards) more deterministic.
Proposed solution
Add a GitHub Action workflow that triggers on:
pull_request event type: opened
Workflow logic:
Check PR metadata (if needed) to ensure it really belongs to NSOC’26 (e.g., branch naming, PR title prefix, or simply label-on-open).
Call GitHub API issues.addLabels (PRs use the same labels mechanism).
Apply label NSOC'26.
(Optional) If label already exists, skip to avoid redundant API calls.
Issue Details
Description
When a Pull Request (PR) is opened, the system automatically applies the label:
NSOC'26This helps categorize PRs related to the NSOC 2026 program immediately upon creation.
Why needed
Improves discoverability and filtering for the maintainers and reviewers.
Enables program-level dashboards, metrics, and easier tracking.
Ensures consistent labeling without relying on contributors to remember it.
Makes review workflows (reviewers, priorities, boards) more deterministic.
Proposed solution
Add a GitHub Action workflow that triggers on:
pull_request event type: opened
Workflow logic:
Check PR metadata (if needed) to ensure it really belongs to NSOC’26 (e.g., branch naming, PR title prefix, or simply label-on-open).
Call GitHub API issues.addLabels (PRs use the same labels mechanism).
Apply label NSOC'26.
(Optional) If label already exists, skip to avoid redundant API calls.