Un-mark workflow deletion
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Description
Currently, marking a workflow for deletion by clicking the delete button updates the deleted_at column in the database and disables all jobs for that workflow. This action results in the project page only showing workflows that do not have a deleted_at timestamp.
However, this process poses two challenges for users:
- Users cannot create a new workflow with the same name as the one marked for deletion.
- Users do not have the ability to un-mark the workflow deletion once it has been initiated.
Steps to Reproduce
- Click the delete button on a workflow.
- Attempt to create a new workflow with the same name.
- Attempt to un-mark the workflow deletion.
Expected Behavior.
- Users should be able to create a new workflow with the same name as the one marked for deletion.
- Users should have the ability to un-mark the workflow deletion if needed.
Additional context
Contributor guide
No contributing guide indexed for this repository
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 reading the linked Mark workflow deletion PR (#605) and trace the workflow deletion flow described in this issue. Done means a deleted workflow can be un-marked and a new workflow can reuse its name, while the existing deletion behavior remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100