fix: when an issue was previously added to project skip instead of throwing#797
Open
jgravois wants to merge 1 commit into
Open
fix: when an issue was previously added to project skip instead of throwing#797jgravois wants to merge 1 commit into
jgravois wants to merge 1 commit into
Conversation
jgravois
commented
Jul 1, 2026
| await addToProject() | ||
|
|
||
| expect(infoSpy).toHaveBeenCalledWith('Skipping issue 2221 because it already exists in project') | ||
| expect(outputs.itemId).toBeUndefined() |
Contributor
Author
There was a problem hiding this comment.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
resolves #389
we've been encountering this old chestnut too so i decided to propose a (naive) patch.