Skip to content

feat(workflow): add GitHub Actions to close linked issues on PR merge - #369

Merged
arutsh merged 1 commit into
mainfrom
Platform/chore/Issue-368/close-linked-issues-on-merge
Sep 30, 2026
Merged

arutsh merged 1 commit into
mainfrom
Platform/chore/Issue-368/close-linked-issues-on-merge

Conversation

@arutsh

@arutsh arutsh commented Sep 30, 2026

Copy link
Copy Markdown
Owner

No description provided.

@vercel

vercel Bot commented Sep 30, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
grant-flow Ready Ready Preview Sep 30, 2026 1:30pm UTC

@arutsh
arutsh merged commit 1c700d3 into main Sep 30, 2026
28 of 29 checks passed
arutsh added a commit that referenced this pull request Sep 30, 2026
#370) (#371)

gh api --jq writes the raw error body to stdout on a failed request, not
just stderr, so `parent=$(gh api ... || echo "")` still captured that
body once the request failed. It then got used as a URL path segment in
the next gh api call and broke. Confirmed live: PR #369's own merge run
closed #368, then crashed exactly this way since #368 has no parent.

Check the command's own exit status instead of trusting the string.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
@arutsh
arutsh deleted the Platform/chore/Issue-368/close-linked-issues-on-merge branch October 10, 2026 09:00

This branch was successfully deployed

1 active deployment
Preview — 7461d4da Deployed Sep 30, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant