Golem commands automatically re-executed after a file change
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 212
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 119
Description
Hello, this is a feature request inspired by the possibility in Scala Build Tool to repeatedly execute a command after a file change.
I'd love to see this feature introduced in the Golem executable. It would be especially useful, for example, during development to automatically rebuild or redeploy an updated version of an agent, but those are just some examples: if implemented for all commands, it would streamline the development process and allow to the user to focus on the code instead of switching between code and terminal.
Additionally, it could be implemented to support a custom delay for the command re-execution.
Example:
golem app ~deploy --delay 40
Expectation:
After 40 seconds of delay from the last file change in the project, rebuild and redeploy the agent automatically.
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 Golem executable's command handling for golem app ~deploy and how it observes project files. Check whether command execution already supports options that could carry --delay. Done means a file change triggers the selected command after the configured delay, including the example's rebuild and redeploy flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100