Implement clean up actions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, kubernetes, shell
- Domain
- ci-cd, devops, infrastructure
Research direction
The issue names no files, tests, or specific entry points. Start by tracing the GitHub Action's cluster lifecycle and reproduce a workflow followed by another run; done means the k3d cluster and its nodes are destroyed after the action so a later run can operate without manual deletion.
Written by the indexing model from the issue text.
Description
It seems like the k3d cluster was not destroyed post action. This means things lie https://github.com/nektos/act cannot operator correctly without manually deleting the existing nodes.
- Dominant language
- Shell
- Stars
- 204
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from AbsaOSS/k3d-action
-
Install only modeOpen
Difficulty 3/5 1-2 days Newbie friendliness 45/100
AbsaOSS/k3d-action#44 · 1 reaction ·
All issues in AbsaOSS/k3d-action
Similar issues
-
release.yml fetches the GitHub CLI keyring with a bare curl, the one workflow download with no retryOpenbug ci phase:10 priority:p3
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
jimmy058910/jmo-security-repo#1629 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
achisolomon/software-factory#182 ·
-
area: docs complexity: trivial documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
accensa/x402-facilitator-stellar#733 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100