syncing a .env file -> github secrets?

@themightychris, any chance you've got tricks up your sleeve for managing this? For some context, the pipeline secrets are safe to be used locally by a small set of developers (e.g. they all access only public slack / github info). It'd make maintaining super easy if I could just update my .env file, and then run a command to have it update github secrets.

Is this crazy? Have you done it before? It feels like something you'd have opinions on!