`bud build` and `bud run` add bogus entry to `go.mod`
Open
Nobody has claimed this yet.
needs decision
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
I think this started happening with pretty recent changes - I'm using v0.1.9:
diff --git a/go.mod b/go.mod
index feb9af9..69e8957 100644
--- a/go.mod
+++ b/go.mod
@@ -136,3 +136,5 @@ require (
// keep in sync with upstream buildkit
replace github.com/docker/docker => github.com/docker/docker v20.10.3-0.20220224222438-c78f6963a1c0+incompatible
+
+replace github.com/livebud/bud => /home/vito/go/pkg/mod/github.com/livebud/bud@v0.1.9
This has an absolute path on my dev machine so I have to avoid accidentally committing it.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue with v0.1.9 by running bud build and bud run, then inspect the resulting go.mod change. Trace where the absolute replace github.com/livebud/bud entry is generated and verify that completing the commands no longer adds a machine-specific path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100