[epic] Improving App Change details
Open
carvel accepted
Epic
priority/awaiting-more-evidence
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
A set of changes intended to improve the observability that the `app-change` feature offers while improving how users interact with stored app changes.
This epic currently includes these issues:
- #338
- #339
- #340
- #341
We are open to suggestions about how we can add more value to stored app-changes. Feel free to put down your thoughts in this thread!
Contributor guide
Research direction
Start by reading the app-change feature and the four component issues (#338–#341) to understand their intended scope. Use those issues to identify the concrete changes and acceptance criteria; this epic itself does not name files, tests, or a definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100