1. Mailing Lists
  2. Contributors
  3. How to use /ocabot merge correctly?

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Salary Structures

Github OCA do not have runbot and codecov in v13

Avatar

How to use /ocabot merge correctly?

by
Ecosoft Co. Ltd., Kitti Upariphutthiphong
- 17/02/2020 10:09:18
Dear community,

We have seen this document, yet it not tell in great detail. https://odoo-community.org/blog/the-oca-blog-1/post/the-oca-github-bot-can-now-merge-pull-requests-92 so may we ask in detailed here,

1) What is the difference between /ocabot merge patch/minor/major and the symantic of x.y.z - breaking.feature.fix in another document. Is it so that,
  - /ocabot merge patch, 13.0.1.0.0 -> 13.0.1.0.1 (patch = fix)
  - /ocabot merge minor, 13.0.1.0.0 -> 13.0.1.1.0 (minor = feature)
  - /ocabot merge major, 13.0.1.0.0 -> 13.0.2.0.0 (major = breaking)

2) For the new [ADD] module, should be click merge manually, or use /ocabot merge (don't want to add any digit, but we test it and it seem to try to change last digit).

3) What is "/ocabot merge" alone, it default to patch or minor?

4) What is the practice to work with some module that has HISTORY. For example, some author (not the PSC), may add in history as new Minor revision, 13.0.1.0.0 -> 13.0.1.1.0 but the merger think it is just a fix. And so, he might do /ocabot merge patch . This could result in the version diff between HISTORY and manifest file?

Thank you!
Kitti U.





Follow-Ups