You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to see added in this software?
Sensitive information mustn't make it into the git history at any moment. Otherwise, when making the SOPs public then, it is necessary to go through the full history to remove those data (which is highly unsafe).
One option was not to recommend the publication of the git repo, only generate HTML with the information redacted. While this would serve the purpose of sharing the SOPs, there could be interesting information encoded in the git history itself, which would make the experiments described by the SOPs more reproducible (e.g., conversations and commit messages can be now used to understand things).
So I can see two options:
have simple yaml/toml files on a private git repo that is added as a submodule
have a mongo installed and store the data there
I would lean towards option 1.
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
No response
The text was updated successfully, but these errors were encountered:
What would you like to see added in this software?
Sensitive information mustn't make it into the git history at any moment. Otherwise, when making the SOPs public then, it is necessary to go through the full history to remove those data (which is highly unsafe).
One option was not to recommend the publication of the git repo, only generate HTML with the information redacted. While this would serve the purpose of sharing the SOPs, there could be interesting information encoded in the git history itself, which would make the experiments described by the SOPs more reproducible (e.g., conversations and commit messages can be now used to understand things).
So I can see two options:
I would lean towards option 1.
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
No response
The text was updated successfully, but these errors were encountered: