Do not sync solution branch?

[yves-chevallier]

I don't know exactly what the expected behavior is, but here is what I have:

An assignment with two branches (private template):

• master with the student's assignment
• solution with the teacher's solution

When I create a new assignment and my student clone the repository I could check (by testing with a dummy user) that only the master branch will be forked with a massive squash on all previous commits. So each student can see only one branch: master with one commit.

And this is exactly what I was expecting. Unfortunately when I created my assignment, this time, every single student could see the solution branch (which was a bad news for me).

Is this a feature or a bug?

[d12]

Including all branches was recently implenented, I wonder if this can be made optional. cc @education/classroom-reviewers

[yves-chevallier]

Oh ! This is a very bad news. We spent some time to came up with a nice workflow and we released our first big assignment to our students. Unfortunately I discovered Yesterday that the solution was then visible and despite none of them pretended to notice it. We simply cannot give them a mark on this assignment, so we had to cancel it (which is also a really bad news in my (evil) plan to convince my colleagues to use GitHub Classroom).

Any workaround known?

[yves-chevallier]

That said, if the behavior changed, I would call this issue a bug and not a feature request :(

[pdvrieze]

This is a feature I would also really want. As a workaround it is possible to have a solution repo (with all code) and a problem repo (with only the base code) where you use a different remote to synchronize only the problem branch to the problem repo.