Closed cfljam closed 10 years ago
Yes, currently what is in github is an instance (from a PFR filesystem), it needs to be a minimal class setup with ideally just the .moa/config for each step, and a installer script to set up on NZGL virtual machines. There is no point maintiaining the set of logs for example.
This just requires a find . | grep -v {wanted} | xargs git rm
&& git commit -am 'spring clean'
&& git push origin master
Done with;
find . -name .moa -type d -exec find {} -type f -or -type l \; | grep -v config | xargs git rm -rf && git commit -m'prune unwanted .moa files'
Just needs a build bash script for each moa step
$ moa new simple
Looks like you need a pull request - your fork is 33 commits ahead.
moa is also automatically interfacing locally and making commits so the streamlining has been undone in the fork .gitignore
?
What about forking and helping out with teh cleaning?
no, I already have a fork which already cleans in a automated way, all that is required in the repo is the .moa/config file to reconstruct all components. The fork was going to propogate those required changes
On Fri, Oct 24, 2014 at 2:23 PM, Helge Dzierzon notifications@github.com wrote:
What about forking and helping out with teh cleaning?
— Reply to this email directly or view it on GitHub https://github.com/biospectrabysequencing/gbs_moa/issues/1#issuecomment-60333153 .
Theses Moa examples are pretty dirty so a spring clean of logs and other stuff belonging in .gitignores is required on a dev branch