Skip to content

fix: when an issue was previously added to project skip instead of throwing#797

Open
jgravois wants to merge 1 commit into
actions:mainfrom
jgravois:patch/389
Open

fix: when an issue was previously added to project skip instead of throwing#797
jgravois wants to merge 1 commit into
actions:mainfrom
jgravois:patch/389

Conversation

@jgravois

@jgravois jgravois commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

resolves #389

we've been encountering this old chestnut too so i decided to propose a (naive) patch.

@jgravois
jgravois requested a review from a team as a code owner July 1, 2026 00:25
await addToProject()

expect(infoSpy).toHaveBeenCalledWith('Skipping issue 2221 because it already exists in project')
expect(outputs.itemId).toBeUndefined()

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i saw a claim on SO that it is possible to get a reference to the relevant itemId on subsequent calls to addProjectV2ItemById, but i wasn't able to corroborate that locally calling addProjectV2DraftIssue.

if its important for there to be parity in the outputs when skipping, i suspect we could fetch it manually.

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.

Workflow fails if issue is already added to project

2 participants