[17.0][OU-ADD] account: Migration to 17.0

[pedrobaeza]

Continuation of #4457

@Tecnativa TT49274

[pedrobaeza]

/ocabot migration account

[pedrobaeza]

@hbrunn do you want to work on the rest?

[pedrobaeza]

This is not working yet.

[hbrunn]

@pedrobaeza can you make this PR writable for maintainers?

[pedrobaeza]

I'm afraid it's something of GitHub itself, as it has been pushed from a organization branch. Feel free to open a new one if you finish it. There's now a CI problem whose roots have been investigated here: Tecnativa/doodba#636

[legalsylvain]

Indeed.

• If pedro creates a branch on his personal space (pedrobaeza) such option are available :

• But if he creates a branch on his organization space (Tecnativa), no option is available.

(tested with my legalsylvain / grap branches)

[hbrunn]

I won't be able to add anything today, will have a look if there's anything left over next Monday

[hbrunn]

PS: Let's then to PRs from our personal forks to facilitate collaboration in the future

[pedrobaeza]

OK, I will continue with this PR during the week.

I won't be able to add anything today, will have a look if there's anything left over next Monday

Yeah, it was the habit, as in our team we always push everything to Tecnativa to promote that collaboration (as others don't have repo maintainer role).

[legalsylvain]

PS: Let's then to PRs from our personal forks to facilitate collaboration in the future

We can also make a PR on OpenUpgrade repo. (OpenUpgrade:17.0-account) So all the maintainers can push on it.
Pro : better collaboration. Cons : corporate OCA statistics doesn't include such work. (= how many PRs are done by tecnativa each years.)
Maybe such things could be done only for 2 or 3 PR per revision, for modules that requires huge work (like account, or base, ...)

[hbrunn]

good idea about pushing to /oca, will do. Continuing this now

[hbrunn]

superseded by #4668