neo4j / neo4j/github-action-traceability
What to do when the Trello API is unavailable.
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
On Nov 30th the trello application and api had issues
I'd like to be able to configure how the action will react if the API is unavailable?
- All trello traceability jobs pass
- All trello traceability jobs fail
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 by locating the action's Trello API handling and its current failure behavior, then trace how action configuration is defined. Done means users can configure whether Trello traceability jobs pass or fail when the API is unavailable, with coverage for both outcomes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- api, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100