Any issues if we made out `prod` branch the default branch in Gitlab?

hi <@U03ES1W5F3J&gt;! let's see what <@U01J549PR6Y&gt; has to say when he sees this

No issue .. i.e. as long as CRIBL_GIT_OPS is set to 'none'It is an issue if the goal is to make your Production read only .. i.e. CRIBL_GIT_OPS set to 'push'

Ahh OK, yes we do have `CRIBL_GIT_OPS=push` set via `systemctl edit cribl` on the prod leader for read-only.Do you happen to know why it would cause an issue?

```[Service]Environment=CRIBL_GIT_OPS=pushEnvironment=CRIBL_GIT_BRANCH=prod```

'push' means that you cannot update the branch directly from Cribl .. only receive information from the branch

Yes correct, but what does that have to do with having the default branch in Gitlab be our `prod` branch vs the unused `main` branch?

aha .. .. nothing .. you can use prod as the default

cool, ty Raanan!