zlacker

[parent] [thread] 3 comments
1. jbergs+(OP)[view] [source] 2020-04-14 17:19:26
I'll bite: They are shifting profits to CI and service landscape. I paid for 8 seats (previous: $64, now: $32) which gave me 10 000 included CI minutes (now: 3 000). I was just at that limit. Its surprisingly hard to find what the cost per minute is after that, but I guess I can check back in a month and see what my spending ends up at.

I'm sure they have enough info about onboarding and unit economics to see how it will pay off mid to long term.

I'll happily pay for use though, it makes sense and it makes the value addition of github core vs extra more clear.

replies(1): >>cf_+nn
2. cf_+nn[view] [source] 2020-04-14 19:05:31
>>jbergs+(OP)
I think it depends on OS (Linux is $0.008/Minute, but macOS is a lot more - like $0.08): https://github.com/features/actions (scroll to the bottom)
replies(1): >>jbergs+jJ
◧◩
3. jbergs+jJ[view] [source] [discussion] 2020-04-14 21:07:48
>>cf_+nn
Ok, so that'd cost me USD$56, leading to a higher monthly than previous pricing. So, steering users toward the Action landscape is obviously a better monetization model.
replies(1): >>jbergs+L01
◧◩◪
4. jbergs+L01[view] [source] [discussion] 2020-04-14 23:04:25
>>jbergs+jJ
Just got an email from Github. Money quote:

> For more than 99% of customers, these changes have lowered their GitHub bills, in many cases quite dramatically. For a very small number of customers who use a large percentage of the free Actions minutes allotment each month, these changes have the potential to cause your bill to increase by $20-50/month, depending on how much you use Actions in the future. To offset that possibility, we’re adding a free credit of $500 to your organization’s GitHub account for you to use in any way you want.

[go to top]