Protecting your credentials whilst publishing code in git (reproducible research): Not sure how much of a common knowledge this is but I often see people use password: "Type your password" in the code and then modify their local versions. By this, they may accidently publish their pass in git history without realising it will still be there even if they remove it in their next commit (fixable of course). Better approach is to set an environment variable. Another approach is to set a local config file that is added to .gitignore. clarify how to use
Deliverables:
We have an article on this - I think. Can you check it out and make improvements so that your insights from above are carefully reflected?
Maybe you want to create a wrapper: "how to deal with passwords", in which you link to the one w/ environment variables.
When closing this issue, check back to the originating issue #1107 and pick another one from the list :)
Deliverables:
Looking forward to your draft and/or questions!