@pedrobaeza
do you mind taking a look at the refactoring/migration if its ok like this?

Please rename the whole commit history with:

git filter-branch --tree-filter 'if [ -d website_odoo_debranding ]; then mv website_odoo_debranding website_debranding; fi' HEAD
git rebase origin/19.0

Please rename the whole commit history with:

git filter-branch --tree-filter 'if [ -d website_odoo_debranding ]; then mv website_odoo_debranding website_debranding; fi' HEAD
git rebase origin/19.0

@pedrobaeza
All done — thanks again for the tip! Learned something new today 😄

@pedrobaeza
Sorry for bothering you again…
First, thanks for the approval and for pointing me to git filter-branch — it did the trick, and I now understand how it works!

I just found out that it’s officially deprecated, though.
Would it be better, in principle, to use git filter-repo for future history rewrites?
Just out of curiosity…

Oh, I didn't know about that. Not sure which is the replacement when that happens...

@pedrobaeza
There is a pip module called git-filter-repo which is recommended.
The equivalent command would look like this:

git filter-repo --path-rename website_odoo_debranding/:website_debranding/ --refs HEAD --force

You can filter a specific branch by replacing HEAD with the branch you want to rewrite.
The --force option can be added to apply the rewrite even if the repository is not a fresh clone.
It seems to produce the same end result.

OK, thanks for the information. Noted for future references.

Ouch, @NICO-SOLUTIONS I told you bad the name of the repository 🤦

Sorry.

It's https://github.com/OCA/server-brand

@pedrobaeza
No Problem. I will Push it against server-brand later on..

superseeded by OCA/server-brand#112