Debugging Tools in UI (e.g. filewatch)

Open
#5,308 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go

Research direction

Start with the file-watching guide at docs.tilt.dev/file_changes.html and compare the existing CLI information with what the UI exposes. Trace the relevant UI and filewatch entry points, then define the global and per-resource views needed to make filewatch debugging possible without relying on the CLI.

Written by the indexing model from the issue text.

Description

enhancement

Describe the Feature You Want

Add UI bits to debug filewatches (globally and per-resource)

Current Behavior

Filewatch information is not available except for the CLI. See https://docs.tilt.dev/file_changes.html.

Why Do You Want This?

The few times I've had to debug filewatches, I found myself stumbling, especially having not used kubectl in years. The guide in https://docs.tilt.dev/file_changes.html works, but unless you know k8s CLI use, it can be a bit overwhelming!

Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tilt-dev/tilt

All issues in tilt-dev/tilt

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.