Hacker News new | past | comments | ask | show | jobs | submit login

How so? The project just includes a script that git clones the forks into your Go workspace for the project /foobar/src....



And then you have to maintain a bunch of ad hoc shell scripts separate from your actual build process. Like I said: fragile and a pain.


Besides a shell script with a "for each repo. git clone", there is no build process (besides running the go build command)...


And of course the fact you're forked off means you can update at your own pace and not have to take someone's ticket to "fix" a "broken" build. While I don't do this forking, it can help control churn, especially in projects with lots of deps.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: