falsedan

5 ms·

1.
by falsedan 9mo ago
oh that makes sense. I thought the OP was suggesting running CI locally instead of a workflow on remote runners
2.
by falsedan 9mo ago
a display of great wisdom, nice
3.
by falsedan 9mo ago
top tip: make a repo in your org for pushing all these nonsense changes to, test out your workflows with a dummy package being published to the repo, work out all the weird edge cases/underdocumented features of Actions once you'r
4.
by falsedan 9mo ago
> You can run all your CI locally if you can, you don't need CI. we can't (too slow, needs an audit trail)
5.
by falsedan 9mo ago
I don't think you're responsible for anything more than your own comments. I added some context that contradicts your assumption that the increased fees were to cover hosting/storage/scheduling costs.
6.
by falsedan 9mo ago
> Having your commits refer ticket ID from system that no longer exists is royal PITA just rewrite the short links in your front-end to point to the migrated issues/PRs. write a redirect rule for each migrated issue/PR, easy ha
7.
by falsedan 9mo ago
we don't need it. we need to run our CI jobs on resources we manage ourselves, and GitHub have started charging per-minute for it. apples and cannonballs
8.
by falsedan 9mo ago
> If you think that's easy I think it's cheap to maintain. let me know how many devs you have, how many runs you do, and how many tests (by suite) you have, and I can do you up a quote for hosting some Allure reports. can sprea
9.
by falsedan 9mo ago
I'm seeing wonky webhook deliveries for Actions service events, like dropping them completely, while other webhooks work just fine. I struggle to see what else could be responsible for that behaviour. it has to be the case that the Act
10.
by falsedan 9mo ago
no, I'd cut the monthly seat cost and grow my user base to include more low-volume devs but realistically, publishing a web page is practically free. you could be sending 100x as much data and I would still be laughing all the way to t
11.
by falsedan 9mo ago
https://github.com/suzuki-shunsuke/pinact
12.
by falsedan 9mo ago
I don't want to shit on the Code to Cloud team but they act a lot like an internal infrastructure team when they're a product team with paying customers
13.
by falsedan 9mo ago
I think you could learn a lot about the other use cases if you asked some genuine questions and listened with intent
14.
by falsedan 9mo ago
it's not the runners, it's the orchestration service that's the problem been working to move all our workflows to self hosted, on demand ephemeral runners. was severely delayed to find out how slipshod the Actions Runner Serv
15.
by falsedan 9mo ago
if you were paying me a monthly license fee for each developer working on your repos, I'd probably consider it
16.
by falsedan 9mo ago
they charge you for artifacts and logs separately, already
17.
by falsedan 7y ago
> Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something. ? Or is it the snarky one, because I’m 100% genuine
18.
by falsedan 7y ago
look, I get that you're not used to being called out on being hopelessly wrong. rephrasing the statement to be an empty tautology so you can be right is a waste of both of our times and only serves to protect your ego
19.
by falsedan 7y ago
Yeah, if government regulations loosened to allow easier access to riskier investments by inexperienced investors or predatory VCs, there would be a lot more stock-based renumeration. Who cares about paying tax on the income generated by th
20.
by falsedan 7y ago
uh HN is not the 'business' of YC. get back to work
21.
by falsedan 7y ago
> SE does not profit from its community websites I don’t see how it’s my problem that their business model isn’t profitable. The board & C-suite still draw a salary, and the company value is built on unpaid labour.
22.
by falsedan 7y ago
amazing, how when even more people are involved with selecting and tagging the input, it becomes even less likely any one person was to blame.
23.
by falsedan 7y ago
Yeah. It's the custom serialisation & schema/ctor arg validation that makes it clunky.
24.
by falsedan 7y ago
> We have volunteer fire fighters, volunteer paramedics, volunteer librarians, volunteer social workers None of these positions are with a private business operating for profit.
25.
by falsedan 7y ago
Jeff seems to have a lot of trouble empathising with users, especially when they want something that clashes with whatever he has discovered is the 'right' solution. See blocklists in discourse, why people join unions, &c.
26.
by falsedan 7y ago
I lost my mind at this sentence. If feels like a first-class data type because the result of parsing is one of the built-in data types (which can be round-tripped to a similar JSON string). And as soon as you care about serialisation of typ
27.
by falsedan 7y ago
yes, when I’m preparing my prestigious project with my Ivy League peers I make sure not to sanitize or vet my inputs so as not to bias the results of my programs or publication success. truly it is remarkable that the training set we chose
28.
by falsedan 7y ago
> Other that that, I tried to get as many big chores done as possible Oh yeah, I cooked 10 kilos of pasta sauce & mince and froze it so we didn’t have to think about cooking.
29.
by falsedan 7y ago
Saw some midwifes, bought some baby stuff. Oh, and I let my work know so I could take some paternity leave. Probably a good idea to get a few nappies, the hospital gave out a couple of freebies but you’re going to want to use more. The seri
30.
by falsedan 7y ago
> don't like the joke this was an attempt at humour? work on those bits some more at the comedy club

More ›