[FEATURE] Add sync-issue-fields composite action

[John McCall (lowlydba)]

Generalizes the inline issue-form-to-org-field sync workflow drafted in tf-data-platform PR #4629 into a reusable composite action, sync-issue-fields. Closes OvertureMaps/tf-data-platform#4625.

Given an issue form with Type/Scope-style dropdown answers, it writes the repo-level issue type and the OvertureMaps org's Scope issue field, both in a single PATCH /repos/{owner}/{repo}/issues/{issue_number}. Confirmed both fields are patchable together against the GitHub REST API OpenAPI spec, and both only need push access to the repo.

Follows check-linked-issue's conventions: composite action, actions/github-script + core.getInput(), pinned third-party SHAs, and a sibling README.

Skips a field if it's already set on the issue (doesn't clobber manual triage), and skips entirely if the issue has no form answers for either field.

Skips instead of guessing

GitHub has no way to trigger a workflow only for issues created from a specific template, so the action has to cope with issues it wasn't meant for:

• No type/scope form answers at all (free-form issue, unrelated template): logs and returns before calling the API.
• A field is already set on the issue (manual triage): dropped from the patch instead of overwritten.
• A form answer's value doesn't match any enabled repo type or field option (a similar-looking template, or a typo): the PATCH call is wrapped in try/catch and warns instead of failing the job.

Field ID is hardcoded, not looked up by name

PATCH .../issues/{n} needs a numeric field_id, and resolving a name to that ID means calling GET /orgs/{org}/issue-fields — which only accepts classic PATs/OAuth tokens with read:org, never GITHUB_TOKEN. Since this action is OvertureMaps-only and field IDs are stable once created, scope-org-field-id defaults directly to the org's Scope field (44814929, found via gh api orgs/OvertureMaps/issue-fields). That means the whole action runs on github-token alone, no second credential needed.

Testing

action.yml parses as YAML; each embedded github-script block was extracted, wrapped in an async function, and passed node --check.

Live-verified the actual write path against a throwaway issue (#68, now closed): PATCH .../issues/68 with type: Bug and issue_field_values: [{field_id: 44814929, value: Base}] applied both in one call, and the response's type.name/issue_field_values[].issue_field_id read back exactly as the skip-if-already-set checks expect. Didn't get a full in-Actions run (GitHub only lets workflow_dispatch target workflows already registered on the default branch, so exercising it live would've meant merging a throwaway workflow to main first) — the parser's field-name-to-key mapping (### Type → type) was confirmed by reading github-issue-parser's source instead of a live run.

Not touching tf-data-platform here, that repo's draft PR will be updated separately to call this action instead of its inline workflow.

[Copilot]

Pull request overview

This PR introduces a reusable composite GitHub Action (sync-issue-fields) to sync issue-form dropdown answers into the repo-level issue type and an org-level issue field, while avoiding overwriting values already set by manual triage.

Changes:

• Added a new composite action that fetches an issue, parses issue-form answers, and conditionally applies a single REST API PATCH updating type and/or issue_field_values.
• Added documentation with example workflow usage, configuration options, and rationale for hardcoding the org field ID.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
.github/actions/sync-issue-fields/action.yml	Implements the composite action logic (fetch, parse, decide updates, PATCH).
.github/actions/sync-issue-fields/README.md	Documents setup, inputs, permissions, and behavior/edge-case handling.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.