surf_wreck21

4 ms·

1. 1.▲
   by surf_wreck21 4y ago

   GH actions has been great for us for CI but incredibly opaque when you're trying to diagnose problems. Simple jobs running on the gh hosted runners are fine, but we have a large pool of self-hosted runners running more complex workflow
2. 2.▲
   by surf_wreck21 4y ago

   I agree; maybe when git was new and actually being used in a decentralized fashion some of the more advanced operations were necessary. But with the typical checkout/branch/PR/merge flow from GitHub and others, I rarely need
3. 3.▲
   by surf_wreck21 4y ago

   Interesting. Having worked at Uber I've been curious why there aren't more of these types of services available to the public.
4. 4.▲
   by surf_wreck21 4y ago

   Github's "require branch to be up to date" setting helps, but doesn't really scale beyond a few engineers in one repo. We tried this where I worked, but after ~6 people, rebasing feature branches got way too annoying.
5. 5.▲
   by surf_wreck21 4y ago

   These are definitely red flags, but it feels like investors (especially at early stages) rarely look at these things. Then in later stages, investors weigh who the early investors are too heavily, and it becomes a big game of emperors new c
6. 6.▲
   by surf_wreck21 4y ago

   It's always been like this for me. I used to respond and engage to build a relationship "just in case", but they churn so fast there's no point.