Manuel Kaufmann

> We are testing _"removing all these old files **on the fly** when serving the page"_ and opt-in into the new addons. Would you like to test this behavior on...

> I didn't activate the addons in my real project (because it breaks my custom flyout placement) Would you help me to get some feedback about the integration I've been...

> However, the CSS file still seems to be loaded the same way (e.g. [just-testing-the-insipid-sphinx-theme.readthedocs.io/en/latest/index.html](https://just-testing-the-insipid-sphinx-theme.readthedocs.io/en/latest/index.html)): Gotcha! Thanks for testing this out. It seems that I missed this URL when removing...

I've been received a few support requests on Read the Docs for Business from users having troubles to re-connect their GitHub repository after it was renamed or moved from/to an...

I'm putting this back into Q2, so we come back to this PR soon.

We are refactoring the flyout completely in our addons implementation: https://github.com/readthedocs/addons/issues/70 The new flyout should not have this issue anymore. We plan to start slowly rolling this out in the...

I updated this branch with the latest changes in `main`. After that, I worked on solving the problem for GitHub and GitLab since they provide the `default_branch` in the incoming...

> I'm removing the command `git checkout --force ` from the steps > executed for this case. This is related to https://github.com/readthedocs/readthedocs.org/issues/9736 in some degree. We can continue following this...

I replied to all the feedback that I receive. There are some good ideas that may require some extra time investigating and decided how to proceed. I suggested to open...

I made some latest changes to make the tests accurate to the changes made on this PR. I also added support for `default_branch` on generic webhooks. It's not a breaking...