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