5 ms·

There is some GitHub used, but as others stated we don't want to create a circular dependency on ourselves in case we deploy something that is broken.

• qppo 6y ago
  Compilers seem to manage just fine with bootstrapping themselves. The trick is not to overwrite yourself
  • StavrosK 6y ago
    You're suggesting they run a second Github somewhere?
    • mappu 6y ago
      I think GitHub Enterprise includes all the features they would need.
• cbb330 6y ago
  Was some mix of decoupling / parallelizing the Actions service considered? I believe the value of dogfooding would be immense. Not only could you become the customer (massive reduction to the deploy/measure feedback loop), but it would be a key marketing move. On top of that, the GUI that will now require critical care and development is essentially a clone of what is offered by Github Actions.
  • jules2689 6y ago
    Yes there was. The change would have been quite a lot to do at once, and we aren't ready to safely add that circular dependency yet. We aren't done on this path, and this certainly won't be the last iteration. I suspect that iteration will come at some point after we can figure out the circular dependency issue. It also makes sense internally. Our actions team is much larger than the team that manages the project I wrote/lead, so it also makes logistical sense IMO We also started before the CD product was ready on actions and we directly influenced it, so yea haha