An engineer selected an organisation starter workflow from the Actions tab three months ago, edited the copied file heavily for the repository, and now the platform team has improved the original template. The engineer expects the repository's workflow to reflect those upstream improvements automatically. Which statement correctly describes what happens to the repository's copy?
- AThe repository's copy updates on the next workflow run, because a starter workflow keeps a reference to its template and pulls in the latest template version each time the workflow is triggered.
- BThe repository's copy stays exactly as it was edited, because selecting a starter workflow makes a one-time copy with no live link, so later template changes never flow into the repository automatically. Correct
- CThe repository's local edits are overwritten when the template changes, because the organisation template is treated as the source of truth and resynchronises owned copies on a schedule.
- DThe repository must reselect the starter workflow to merge the changes, because GitHub offers an automatic three-way merge that combines the new template with the repository's existing edits.
Why A is wrong: Tempting because reusable workflows do track an upstream reference, but a starter workflow is a one-time copy with no live link, so it does not pull template changes on a run.
Why B is correct: A starter workflow is copied once into the repository at selection time, so the repository owns that file outright and upstream template edits do not propagate to it automatically.
Why C is wrong: Tempting because central governance often overwrites copies, but a starter workflow grants full ownership to the repository and never resynchronises or discards the repository's own edits.
Why D is wrong: Tempting because reselecting could fetch the newer template, but GitHub performs no automatic merge with existing edits and would create a separate new file rather than merging into the customised one.