falsedan

oh that makes sense. I thought the OP was suggesting running CI locally instead of a workflow on remote runners

a display of great wisdom, nice

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're done, make the actual changes in your real repo. I call the test repo 'pincushion'

> You can run all your CI locally

if you can, you don't need CI. we can't (too slow, needs an audit trail)

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.

> 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

hard-coded links in commit messages are annoying, you can redirect in the front-end too but locally you'd have to smudge/clean them on local checkout/commit

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

> 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 spread the up-front costs over the 3-year monthly commitment if it helps

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 Actions service emits events that trigger webhook deliveries & sometimes it messes them up.

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 the bank

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

I think you could learn a lot about the other use cases if you asked some genuine questions and listened with intent

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 Service was, and had to redesign to handle out-of-order or plain missing webhook events. jobs would start running before a workflow_job event would be delivered

we've got it now that we can detect a GitHub Actions outage and let them know by opening a support ticket, before the status page updates

if you were paying me a monthly license fee for each developer working on your repos, I'd probably consider it

they charge you for artifacts and logs separately, already

> 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

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

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 the difference between strike & fair market value if the grant also comes with a cash bonus exactly equal to the tax burden (and its income tax)?

EU banks have massive IT organisations and budgets so can afford to pay through the nose for contractor day rates. That's the ticket for frontline grunt wealth, and also the source of a lot of the risk-adverse 'bankist' mindset in a lot of experienced tech workers.

uh HN is not the 'business' of YC. get back to work

> 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.

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.

Yeah. It's the custom serialisation & schema/ctor arg validation that makes it clunky.

> We have volunteer fire fighters, volunteer paramedics, volunteer librarians, volunteer social workers

None of these positions are with a private business operating for profit.

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.

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 types it starts feeling incredibly clunky.

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 to use is racist but no single person who could have stopped this or be held responsible is

> 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.

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 serious answer is, there’s nothing we can think of and say, oh I wish we’d done/had that. Be ready for a lot of disruption and learning on short notice and bonding with a new person who’ll depend on you for everything and is working really hard on improving their communication.

Oh you’ll probably also benefit from knowing where the hospital is, how to get there, where to park/get off the bus, &c.

> don't like the joke

this was an attempt at humour? work on those bits some more at the comedy club