roubaobaozi

Version control strategy

Recommendation

1. Repo #1: contains the central functions, subject to gitflow branching methodology or with a repo gatekeeper.
2. Repo #2: separate trees of work. Each user has one branch that will be their develop, eg. develop-navid, develop-otherperson etc. Off those branches, each user creates their feature branches (twigs, eg. feature/navid-work-part-one.) Squash feature branches to a single commit before merging back into their own develop-navid or whoever, to keep commit histories clean. Into separate folders, clone that fastai by version (this will keep local copies by version in your own repo, making it much larger, but at least you can keep separate versions of the code for your old and new notebook things.)

Read about gitflow here: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow

Get me the freshest code

roubaobaozi

<p><a href="#">test</a></p>
<p><a href="#">test</a></p>
<p><a href="#">test</a></p>
<p><a href="#">test</a></p>
<p><a href="#">test</a></p>
<p><a href="#">test</a></p>
<p><a href="#">test</a></p>
<p><a href="#">test</a></p>
<p><a href="#">test</a></p>
<p><a href="#">test</a></p>

roubaobaozi

<div class="someclass notip">notip</div>
<div class="someclass">not notip</div>