temporalio / temporalio/skill-temporal-developer
Workflows don't fail for this reason unless this is opted into, which is a good idea for tests. We should consider noting how to opt-in to this somewhere.
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 220
- Forks
- 30
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 14
Description
Workflows don't fail for this reason unless this is opted into, which is a good idea for tests. We should consider noting how to opt-in to this somewhere.
Originally posted by @cretz in https://github.com/temporalio/skill-temporal-developer/pull/4#discussion_r2788818235
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, test, or entry point is named. Start with the linked pull-request discussion and identify the workflow failure condition and its opt-in setting; done means adding a clear note explaining how tests enable it.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100