'Please clean your repository working tree before checkout.'

[BethDibnah]

Hi, I was trying to follow along to the livestream today but got stuck in the set up.. I synced my forked repo on Github, but when going back to Positron to pull, I get this error message:

I can see there are some staged changes, but I have no idea where they came from. I tried to commit these and something else started to happen and they didn't commit, so I'm a bit stuck on what to do and the console keeps updating with new info that I have no idea what it is.. screenshot is attached! Any help would be great, as I am very confused. Thanks!

[DavidRach]

Hi @BethDibnah, uff, this might get messy.

First off, if you have any files that you wrote or have added to that local CytometryInR folder (in the homework folder or otherwise), go ahead and copy them over to another location so that they are backed up and not lost.

You have a couple options. Easiest would be to delete the entire CytometryInR folder on your local computer, and just re-download it from your GitHub ( https://github.com/BethDibnah/CytometryInR ) using the New Folder from Git option.

You could also hover over the "Fix of the n of 20 challenge question commit", copy the commit hash number, and then once you have copied any of your files out, enter the following in the terminal tab

git rest  --hard AndPasteTheHashNumberHere

Which will roll out a hard reset, rolling back the clock to that point in the repository. You would then be able to pull, bringing in all the changes that are currently stalled.

There may also be a third option, generally in the bug console window from the screenshot above, the helpful trouble shooting options are about a full scroll above, in which case, screenshot those for future reference?

Hope this helps get the repository unstuck.

Best Wishes-
David

[BethDibnah]

Hi David, Apologies for my late reply, I have been off for a couple of weeks! Thanks for your help with this, I had no idea what had happened. I just deleted the folder and redownloaded like you suggested and this seemed to fix the problem 😊 Thanks again!