What's changed
Breaking: task ids are now read only from the three places where a pull request states what it delivers.
| Source | Read? | Example |
|---|---|---|
| Branch name | yes | feature/ABC-123-do-the-thing |
| Pull request title | yes | ABC-123 Do the thing |
| Changelog link in the body | yes | - [ABC-123](https://example.com/task/ABC-123) What changed. |
| Anything else in the body | no | - other/repo#12 (`ABC-123`) |
| Commit messages | no | The ABC-123 patch still applies, it touches another file. |
Previously every match of the task id pattern anywhere in the full message of every commit, and anywhere in the body, was reported as delivered work. A task mentioned in passing was therefore picked up by whatever the workflow did next — moving statuses, reassigning, overwriting links — and since task ids are unique across a workspace, that reached tasks of entirely unrelated projects.
Only the text of a markdown link counts as a changelog entry, so [the ABC-123 preview](https://example.com) no longer qualifies.
Commits are no longer fetched at all, which drops one API call per run.
When none of the three sources yields an id, the action logs a warning and sets an empty task_ids output.
No changes to inputs (token, task_id_pattern, pull_number) or the task_ids output.
Upgrading
If you relied on ids in commit messages, make sure the task id is in the branch name, the pull request title, or a changelog link in the description.