dapirian

4 ms·

1.
by dapirian 4y ago
Hey thanks for the Q: We will support other CI systems than GitHub Actions, but exact timeline of which and when is TBD. With regards to cost, you can self-host GitHub Actions runners. Internally we use an autoscaling group of spot instance
2.
by dapirian 4y ago
In SF, $35/walk is cheap. If you've watched 10hrs of dog training videos on youtube you can command $100/hr (the going rate for an unqualified dog trainer), or $150+/hr for a qualified dog trainer.
3.
by dapirian 4y ago
Especially if you're using a finite pool of CI runners. Lots of companies do run their own CI runners either for added security, or to get persistent CI machines with a hot local cache so builds/tests are much faster. Then everyon
4.
by dapirian 4y ago
I think this definition is outdated - linters find real bugs now. The boundaries between linters, static analyzers, and security tools in real life are basically nonexistent, it's entirely tool by tool. Also, autoformatters should styl
5.
by dapirian 4y ago
why?
6.
by dapirian 4y ago
If each of your commits are tested and make sense independently, they should be different PRs - sounds to me like you're just smashing 5 stacked PRs into 1 with highly fussy curated commits, which aren't guaranteed by github setti
7.
by dapirian 4y ago
> As for squashing, I believe that everything should be rebased instead to maintain a proper, linear git history Rebasing on your PR branches is up to you, it's subjective, but setting GitHub to rebase your PR commits onto your main
8.
by dapirian 4y ago
Trunk Merge is an intelligent service that orchestrates merging pull requests to maintain a repository of code that always passes tests. Airbnb, Uber, Twitter, Robinhood, and many other big tech companies internally have their own sophistic
9.
Trunk Merge(trunk.io)
14 points by dapirian 4y ago|5 comments
10.
A better way to merge code(blog.trunk.io)
3 points by dapirian 4y ago|0 comments
11.
Show HN: Trunk detects and handles preexisting linter issues(blog.trunk.io)
3 points by dapirian 4y ago|0 comments
12.
by dapirian 4y ago
true story
13.
by dapirian 5y ago
100% agree that documenting the practices of your repo is a losing battle: automate it or don't bother. I don't think you go far enough here. Every file in your repo should minimally have an autoformatter and some kind of linter&#
14.
Ultra-clean sane configs for linters, formatters, and more(github.com)
3 points by dapirian 5y ago|0 comments
15.
by dapirian 5y ago
Thanks for the comment! Go ahead and use it in private repos for personal use or on small teams for free - our pricing structure only targets private repo use by companies with eng teams > 10. Even for ecosystems that do have tool dep pi
16.
by dapirian 5y ago
Hey thanks - it should populate with issues for any files that you've modified, and as you browse files any file you have open. We don't have a way from vscode to run on the whole codebase yet, best run the cli for that, but it&#
17.
by dapirian 5y ago
thanks semil!
18.
by dapirian 5y ago
Hi! I’m one of the co-founders of Trunk. Trunk Check is the first tool in the toolbox we're building to make scalable, productive repos possible out of the box. Modern repositories include many technologies, each with its own set of l
19.
Show HN: Trunk – One linter to run them all(trunk.io)
38 points by dapirian 5y ago|8 comments