Why?

This depends on your reverse proxy. Nginx e.g. needs to be restarted (down time).
This is a more manual process.
Just this doesn't provide HA.

Have you ever used K8s? And just to say it: if no one would need it, it wouldn't exist...

Name a good solution?

or you need HA and zero down time upgrades 🤷

nobody is wrong, but it depends on the use case. It is not a solution for every use case or every user. The same as for the most technologies...

Naja, anrechnen geht schon, nur komplizierter 🙃

Wir hatten im Pribzip jedes Semester 6 Module à 5 ECTS alsi 30 ECTS pro Semester

Eigentlich alle Module 5, im Bachelor hatte ich zwei die 2,5 gaben und eins was 10 gab, dass war aber im Prinzip zwei Module in einem.

Ok, so you "temporarly" merge the feature branch in the CI?<li>Never saw this in the real world...</li><li>How does this work with merge conflicts? Most of the merge requests I see at work have merge conflicts. The CI wouldn't be able to fix them. And if you now pull main into your branch, we have the same situation as above, so why not just always do that?</li>

If I run the CI against the latest commit of the feature branch it is not guranteed that changes in main not in your branch will break the code?

Or I don't understand what you mean.

Ok, then not rebasing, instead merge main into the feature branch.

If I run the CI against the merged result (feature in main) it is too late for such issues. Then main is already broken...

I also think it would be the responsibility of the person who want to merge their stuff. If it is a rebase or merge is unrelated

Why?

I experienced way too often that a feature branch worked perfectly fine, tests were successful etc. Then it is merged in main and there was a change in some code which the feature branch uses etc and it breaks.
To prevent this, get the branch to the latest state before merging, build it and run tests. Afterwards merge it.

Otherwise I don't know a better way to prevent breakage on main.