neo4j / neo4j/github-action-traceability
Allow public repositories to use a comment-based approach
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Author should:
- create a PR comment containing a Trello URL
GHA should:
- validate the URL does not leak data
- attache the PR URL to the Trello card
- give the all clear
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
No file or test is named. Start at the GitHub Actions entry point and trace how pull-request comments and Trello URLs are currently handled. Done means a comment URL is validated, the pull-request URL is attached to the Trello card, and the action gives the all clear without leaking data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100