neo4j / neo4j/github-action-traceability
Duplicates PR on Card
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
@sherfert and @mnd999 have both reported issues when there are duplicate PR attachments on a Trello card. If a user deletes one attachment, the bot will add it back.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no source file, test, or entry point. Start by tracing the code that synchronizes pull-request attachments with Trello cards, then reproduce the duplicate-attachment case described in the report. Done means deleting one duplicate attachment does not cause the bot to add it back.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100