Ability to define a task which is always called after an action chain workflow finishes (either fails or succeeds)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
It would be useful if user could define a step which is always called when a workflow finishes and / or fails. You can think of it as "finally" in Python and other programming languages.
Similar end result can be achieved by adding "on-failure" to every step, but defining this function once is nicer.
Here is an example from a workflow I'm currently working on:
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 names no files, tests, or entry points; start by tracing how action-chain workflows detect successful and failed completion. Define the workflow boundary and identify where a single final step could be invoked for either outcome, then add coverage showing that it runs after both success and failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100