Repository navigation
TeaScript Lore ‐‐ The Lost Version
TeaScript's first version ever, v1.0.0-beta.1, lovingly referred to as 'The Lost Version', got its name from the fact that no one can access it, as it was deleted by the owner (me!) of the previous TeaScript repo, along with it all.
Imagine this. You have left your local code untouched for a few days. Then, you make some changes on the remote. Then, you make more changes to the local code. You add a few more features, dependencies, and everything is OK! Until you have to push your changes. You have to fetch from the repo, and when the time comes for you to merge, IntelliJ IDEA leaves you in the dust. The git tool is useless, so you try to manually edit ALL of your files that were affected. Despite your valiant efforts, you give up. You desperately try to revert your changes by editing the history. BIG MISTAKE. As you realise the extent of the damage done to your repo, you decide there is only one thing you can do now. You clone the code you have locally and delete the repo, along with most of the problems that arose in the process.
But now, you have a whole repository to fix up. It takes ages, and you DO lose some progress, but order is restored. Since then, I have always kept a local backup of my code at all times. I have also updated IntelliJ IDEA, and now, when I need to merge, it provides the tools it failed to provide in my time of need. You can even look at some of the earlier commits and review their code.
Make sure to ALWAYS have a backup or copy that closely mirrors your code. Do not neglect setting up branch protections either.