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
Right now abc-author adds all assignments to the student directory. Similarly abc-distribute will generate a PR that modifies everything.
Instead we want to have abc-author assignment1 which only adds assignment1 related files to the already existing student/ directory. abc-author -d assignment1 would remove the assignment from the student/ directory again.
abc-distribute (w/o arguments) would generate a PR based on everything in student/ (copy over whole student/ directory). abc-distribute assignment1 would only create a PR with changes for that assignment (copy over only the assignment specific sub-directory from student/).
One thing that will be tricky to figure out is the .circleci/config.yaml which we will need to edit as we do this.
The text was updated successfully, but these errors were encountered:
I had another thought about this yesterday @betatim Right now what works well is each time i distribute content we reset the PR in the student's directory. This handles the student that maybe misses the first assignment for whatever reason or any assignment. Is there a clever way to still ensure that we don't get PR merge conflicts for the students?
Right now
abc-author
adds all assignments to the student directory. Similarlyabc-distribute
will generate a PR that modifies everything.Instead we want to have
abc-author assignment1
which only adds assignment1 related files to the already existingstudent/
directory.abc-author -d assignment1
would remove the assignment from thestudent/
directory again.abc-distribute
(w/o arguments) would generate a PR based on everything instudent/
(copy over wholestudent/
directory).abc-distribute assignment1
would only create a PR with changes for that assignment (copy over only the assignment specific sub-directory fromstudent/
).One thing that will be tricky to figure out is the
.circleci/config.yaml
which we will need to edit as we do this.The text was updated successfully, but these errors were encountered: