Improve self-development workflow
Open
Nobody has claimed this yet.
kelos/needs-input
kind/feature
needs-actor
priority/important-longterm
triage-accepted
- Dominant language
- Go
- Stars
- 331
- Forks
- 40
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 70
Description
Currently, I need workarounds to cover the case kelos natively cannot handle.
e.g. /reset-worker /squash-commits
How can I redesign the crd?
Goals:
- replace reset-worker, squash-commits workflow
- handle pull request based workflow without issue (simple patch)
Let's make a plan first.
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 reviewing the current CRD and the existing /reset-worker and /squash-commits workflows. Compare them with the pull-request-based workflow described in the goals, then document a plan that replaces those workarounds and supports simple patches without an issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100