Dear Seqinspectors seqinspector logo green in this <!channel>, New year, new resolutions and…a new fork. Maxime and I have been cleaning the Git history of the repository, such that the size of a fresh fork now went down massively: The whole repository now is just 8% of its previous size 📦🤏🏻. BUT: The whole time traveling did cause some disruptions in the Git continuum. This means that it will be difficult to merge in new contributions cleanly, if they come from a different parallel universe 🌃 . Particularly if you start new work, you thus need to update your forks. The safest and easiest is, if you delete your entire fork. To do that, navigate to the Settings and scroll down into the Danger Zone. Then delete the repository. Afterwards, do not forget to also remove your local clones, e.g. with

rm -rf seqinspector

. Now, you need to recreate your fork (or use the GUI)

gh repo fork nf-core/seqinspector --fork-name nf-core-seqinspector --clone

After you recreated your local clone, you should see something like this with

git remote -v

git remote -v
origin	<https://github.com/YOURGITHUB/nf-core-seqinspector.git> (fetch)
origin	<https://github.com/YOURGITHUB/nf-core-seqinspector.git> (push)
upstream	<https://github.com/nf-core/seqinspector.git> (fetch)
upstream	<https://github.com/nf-core/seqinspector.git> (push)

Now, you can happily start working on new features for version 1.1 🎉