For @Cris Tuñí, @Adam Talbot , @Erkut Ilaslan and @Pontus Höjer : Your pull requests have been rebased and are now available as branches on the repository: • Add kraken2 phylogenetic assignment subworkflow #47 is now pr/47 • add bbmap clumpify #52 is now pr/52 • Adds FASTQE for summarising FASTQ scores as emojis #66 is now pr/66 • Adds fq/lint for early validation of FASTQs #67 is now pr/67 • Add sequali #134 is now pr/134 You can now either change the base of your pull requests to those branches and delete your entire fork (recommended) or fetch those rebased branches as new branches into your existing forks until the respective PRs have been merged. In either case, you need to fetch that branch (there PR 47 for example)

git fetch upstream pr/47
git checkout pr/47

Then either push to a new branch and change the base of your pull request:

git push origin --set-upstream pr/47:pull47

or force push over your existing branch (here be dragons)

git push --force-with-lease origin pr/47:feature/kraken2

In either case, your pull requests should afterwards have a moderate number of commits. If you see a diff of hundreds of commits and files, you are still on an old branch:

Fantastic! Thank you for the heads up, I'll fix this ASAP