Add work item linkage information to job summary and notices

[Copilot]

Summary

Re-implemented the work item visibility feature after branch was reset to main.

Changes Made

1. Work Item Linkage Visibility

• GitHub Actions Notices: Added core.notice() calls when work items are linked, displaying annotations in the workflow run

  • For commits: Work item AB#12345 (from commit abc123d) linked to pull request #42
  • For PR title/body: Pull request linked to work item AB#12345

• Job Summary: Added entries to core.summary that appear on the job summary page

  • Includes clickable markdown links to commits
  • Provides quick reference of all linked work items

2. Test Updates

• Updated __tests__/index.test.js to mock core.notice and core.summary
• All 51 JavaScript tests passing
• All 29 bash tests passing

3. Documentation

• Added "Action Output" section to README.md explaining the new visibility features
• Updated Key Features list to include visibility & tracking

Testing

✅ All 80 tests passing (51 JS + 29 bash)
✅ Action successfully packaged to dist/

Files Changed

• src/index.js: Added core.notice() and core.summary calls when work items are linked (36 lines added)
• tests/index.test.js: Added mocks for core.notice and core.summary (13 lines added)
• README.md: Added "Action Output" section documenting the new visibility features (10 lines added)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add information on linkage to job summary or ::info</issue_title>
<issue_description>From the job, make it easier to see what work item(s) were linked to PR

  echo "Pull request linked to work item number: $WORKITEM_NUMBER"
  # TODO: validate work item?
  # TODO: add this as an ::info or to the job summary?</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #68

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[joshjohanning]

@copilot can you rebase and re-make these changes? I changed my action pretty significantly since originally requesting this (now native node action and not composite action with shell).

[Copilot]

@copilot can you rebase and re-make these changes? I changed my action pretty significantly since originally requesting this (now native node action and not composite action with shell).

I've rebased and remade the changes for the new native Node.js action structure. The changes are now in commit 77cd7b0.

What Changed:

• Added core.notice() annotations when work items are linked (visible in workflow run annotations)
• Added entries to core.summary for the job summary page with clickable links
• Updated tests to mock the new core functions
• Updated README with Action Output documentation

The functionality is the same as the original PR, but now works with the ES modules-based action instead of the old composite shell action.

[joshjohanning]

@copilot I had to manually git fetch origin main && git reset --hard origin/main to get the latest in this working branch. Now you have to re-implement the original requirement.

[Copilot]

@copilot I had to manually git fetch origin main && git reset --hard origin/main to get the latest in this working branch. Now you have to re-implement the original requirement.

Re-implemented the work item visibility feature in commit 42a4fac.

Changes:

• Added core.notice() annotations when work items are linked (visible in workflow annotations)
• Added entries to core.summary for the job summary page with clickable links to commits
• Updated tests to mock the new core functions
• Updated README with Action Output documentation

All 80 tests passing (51 JS + 29 bash).