improve visibility of pending changes for manual resources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
When a resource has TRIGGER_MODE_MANUAL and I've changed relevant files, I want to clearly know there are pending/unapplied changes and be able to make an informed decision about whether to trigger an update.
Current Behavior
There are 3 icon states for the rebuild button:
trigger mode auto
(afaik it's always like this for auto resources)
trigger mode manual (no pending changes)
Tooltip: Trigger update
trigger mode manual (pending changes)
Tooltip: Trigger update to sync pending changes
I think these are too subtle and easy to miss. We also don't convey that information in expanded form (i.e. in the resource pane) nor do we show the list of pending files to help make a decision about whether to rebuild (see #1814).
Why Do You Want This?
- Decide whether to trigger an update based on what's change
- Not feel like Tilt is broken because I forgot something is in manual and nothing is happening
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 locating the rebuild button and resource pane UI, then review issue #1814 for the pending-file details referenced here. Done should make pending changes for manual resources clearly visible, expose the relevant pending files, and help users decide whether to trigger an update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100