add reaction should handle locked issue

[pelikhan]

The add rection handler should silently ignore failure to set a reaction (log it to core.info) when the issue is locked.

See failure in https://github.com/github/gh-aw/actions/runs/22040043419/job/63679342442

[pelikhan]

/cloclo

[github-actions]

✨ Claude Response via /cloclo

Summary

I've fixed the issue! 🎉 The add_reaction handlers now gracefully handle locked issues, PRs, and discussions by silently logging instead of failing the workflow.

What I Did

🔧 Modified 4 files:

1. actions/setup/js/add_reaction.cjs - Added smart error detection:

   • Detects 403 errors with "locked" or "Lock conversation" in the message
   • Logs an info message instead of failing
   • Other errors continue to fail as expected

2. actions/setup/js/add_reaction_and_edit_comment.cjs - Same fix for the combined handler

3. Test files - Added comprehensive test coverage:

   • ✅ Locked issues with 403 status → silently ignored
   • ✅ Locked issues from message text → silently ignored
   • ✅ Non-locked 403 errors → still fail (correct behavior)
   • ✅ Other errors → still fail (correct behavior)

Test Results

All 46 tests passing! 🚀

Test Files  2 passed (2)
Tests       46 passed (46)

Pull Request Created

I've created PR with all the changes. The fix is ready for review and merge!

Technical Details

The solution uses this logic:

const is403Error = error?.status === 403;
const hasLockedMessage = errorMessage?.includes("locked") || 
                         errorMessage?.includes("Lock conversation");

if ((is403Error && hasLockedMessage) || (!is403Error && hasLockedMessage)) {
  core.info('Cannot add reaction: resource is locked (this is expected and not an error)');
  return;
}

This ensures we only ignore the specific "locked" errors while maintaining proper error handling for all other cases.

---

🎭 With style and glamour, just like Cloclo!

🎤 Magnifique! Performance by /cloclo for issue #15966