https://github.com/skills/reusable-workflows This gave me the model to understand how the matrix + reusable workflow works. A single value is passed to the reusable workflow. The parent workflow generates the parallel jobs.
I'm sticking with the .env strategy here. Let me know if you think there's a better alternative.
what about creating a .env in the repositories with commented lines , showing the variables that should be defined
I tested to see if we could add .env with comments and then also include it in .gitignore, so that no one can accidentally commit and push credentials, but it doesn't work. If you ever add a file to tracking, even if in .gitignore, is always tracked. I think for safety and security we should never allow a .env in our git repos.
I'm open to push back, but I think this is common practice.
Originally posted by @beauremus in #2 (comment)
I tested to see if we could add .env with comments and then also include it in .gitignore, so that no one can accidentally commit and push credentials, but it doesn't work. If you ever add a file to tracking, even if in .gitignore, is always tracked. I think for safety and security we should never allow a .env in our git repos.
I'm open to push back, but I think this is common practice.
Originally posted by @beauremus in #2 (comment)