document how to resolve “how can i tear down an earlier step when a later step fails?”
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Go
- Stars
- 24
- Forks
- 19
- Avg merge
- 11m
- Merged PRs (30d)
- 2
Description
run the explicit step in self destroy. (not required to always run every step)
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
Start by locating the documentation that covers explicit steps and self-destroy behavior. Clarify how to tear down an earlier step when a later step fails, including whether every step must run; done when the documented procedure answers the question without requiring an unresolved design decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100