is now the time to comin it up

[mehbark]

i actually don't know

[kurisufriend]

yes!
maybe. how does it handle switching to a dev branch? do you have to push a change to the gitops-tracked main to specify that all further changes should come from watching a different branch? are these questions that could trivially be answered by rtfming?
i like the name

[mehbark]

the point in my mind is that the mainster branch is the source of truth, but i guess that conflicts with vtluug's test in prod style

[kurisufriend]

we don't really have a non-prod to test in :/

[kurisufriend]

like, if you're working on a PR for a feature, what do you do if it merges and doesn't work? make a second feature branch and PR that? it doesn't allow for great iteration. there is probably an existing solution for this that people with jobs do

[mehbark]

I think we'll probably end up doing a pseudo-not rocket science thing where we

1. change stuff in branch
2. nix run .#deploy
3. trust me bro it works
4. merge into main
5. comin automagically switches to the new main

and we always ~know that main is safe to switch to when things go wrong. we could make some checks and smoke tests (e.g. pinging certain services)