Scenario: We have an assignment released in our public repo. Students pull, work on assignment A. A week later, this assignment gets removed from our repo due to a forced push. Students click link to load in other assignments. Students then see merge issues with their version of the assignment A. Inspection reveals that their copy of assignment A is staged for commit. Students continue to see these issues even after assignment A is restored to the repo.
Expected behaviour
Once Assignment A was restored to the repo, students would no longer see merge issues.
Actual behaviour
Students are unable to sync any other assignments due to a merge conflict with assignment A.
How to reproduce
Push a file to the repo.
Use nbgitpuller to pull a copy of the repo.
Edit the file.
Remove the file from the repo through a force push.
Add another file to the repo.
Try to use nbgitpuller to pull a copy of the repo again.
Your personal set up
I am a course staff member of Data 100 @ UC Berkeley, we are using data100.datahub.berkeley.edu. I do not know the particular configuration.
Bug description
Scenario: We have an assignment released in our public repo. Students pull, work on assignment A. A week later, this assignment gets removed from our repo due to a forced push. Students click link to load in other assignments. Students then see merge issues with their version of the assignment A. Inspection reveals that their copy of assignment A is staged for commit. Students continue to see these issues even after assignment A is restored to the repo.
Expected behaviour
Once Assignment A was restored to the repo, students would no longer see merge issues.
Actual behaviour
Students are unable to sync any other assignments due to a merge conflict with assignment A.
How to reproduce
Your personal set up
I am a course staff member of Data 100 @ UC Berkeley, we are using data100.datahub.berkeley.edu. I do not know the particular configuration.
Full environment
Configuration
Logs