Fix action failure when pull request is closed without merging

[Copilot]

The action was failing when processing pull requests that were closed without merging, throwing a "Cannot iterate over null" error during the content metadata parsing step.

Root Cause

When a pull request is closed without merging, the GitHub GraphQL API returns null for the node in the query response. The fetchContentMetadata function was attempting to access result.node.projectItems.nodes without first checking if result.node was null, causing the action to crash.

Solution

Added a null check for result.node in the fetchContentMetadata function. When the node is null, the action now:

• Sets a clear error message indicating the content was not found or is not accessible
• Returns an empty object to gracefully handle the failure case
• Prevents the crash and provides better debugging information

Additional Fix

Also resolved an unrelated bug in the convertValueToFieldType function where it was checking for fieldType === "NUMBER" instead of fieldType === "number", causing number field conversions to fail.

Testing

• Added test case for the null node scenario
• All existing tests continue to pass (31/31)
• Verified the action builds and packages correctly

Before this fix, users would see:

jq: error (at organization-Breadcord-issue-PR_kwDOItt-hs5Gk46V.json:0): Cannot iterate over null (null)

After this fix, users will see a clear error message:

Content not found with ID PR_kwDOItt-hs5Gk46V - it may have been deleted or is not accessible

Fixes #12.

---

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