Exactly, you never check passwords into version control. So what happens when you need to share those values with other team members? The github example is not to put a .env file into a repo but to add the secrets to github’s native secret manager, which is what products like actions use to read envs.

Not currently but it is planned to be added soon along with in-client conflict resolution.

I actually did consider rewriting it to use Tauri over electron, but found it didn’t fit to my pipeline or offered everything I needed,

Yes, it’s a visual git client (like GitHub desktop or fork)

Yeah, sorry about that.

It’s currently private as I still have a bit to go until beta testing but the site assumes it’s public.

I’ll disable the button and stop the automatic redirect!