Timeline for Private and Public version of repository with minor difference
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 13, 2019 at 17:35 | comment | added | Throckmorton | Yes, that sounds like the automated version of what I'm doing now :p. Ideally, I was hoping there would be a way to somehow link them via version-control. Something akin to a psuedo-merge of the two repositories would make things much easier | |
| Nov 13, 2019 at 17:33 | comment | added | Jon Raynor | Ahhh, you could still potentially signal sections of code to be internal/external, but you would have to have a pre-porcessor to go through all your scripts and strip out the internal parts and data. Doable, but more complex. | |
| Nov 13, 2019 at 17:30 | comment | added | Throckmorton | So the code is not compiled. It is a set of scientific scripts and workflows. The application also ships with data. The private version has some additional private data as well. So there are explicit sections that shouldn't be able to even be seen by the public version. | |
| Nov 13, 2019 at 17:27 | history | answered | Jon Raynor | CC BY-SA 4.0 |