Automatically commit blacklisted ports

[sebalix]

This change is not backward-compatible.

This feature will store blacklisted PR or module migration in a ./oca-port/blacklist/{MODULE}.json file (one file per module) and this will be committed in the working branch so this information will be shared with other contributors (PR or module blacklisted won't be listed anymore, but the reason why it was blacklisted will be displayed instead).

Here is a demo of a blacklisted PR with the current changes: OCA/wms#464

fix #4

[sebalix]

I wonder if we should add a comment when we blacklist something, explaining the reason why we did it (changes already ported, lint, doesn't apply anymore, module replaced by another one or renamed...)

[ivantodorovich]

I suggest to store this file in .oca/oca-port/blacklist/{MODULE}.json (or similar)
Goal is to put it under an .oca directory that we can use for (possible) future oca tools

Also maybe use a yml file instead of json, that's more common than json in this kind of tools

[sebalix]

@ivantodorovich good ideas. For YAML the only drawback is to introduce a new dependency, while JSON is part of the Python std lib.

[simahawk]

I agree on the path, I agree on keeping JSON. And, yes, let's collect a comment!

[sebalix]

@simahawk I'll try to pop-up the editor during the git commit, or add a user input in the commit message. I don't think we need to store this in the JSON file.

[sebalix]

Here is a demo of a blacklisted PR with the current changes: OCA/wms#464

[sebalix]

I'm quite happy with these changes at the moment, and want to build a new release for that, so... merging :)