Per-developer secrets best practice

Hi all,

Is there a GitHub best practice for dealing with multiple sets of secrets? We have sets of secrets that are unique to each developer as well as a common set for staging and a common set for production.

Thanks

2 Likes

That kind of sounds like a case for using forks. Each developer could use their own secrets in their fork of the repository, and then the common set could be configured in the central repository where code gets merged.

1 Like