Skip to Content

Contributors

  • Re: Travis logs full of "INFO openerp_test odoo.schema: Keep unexpected index"
    Hello Olaf,

    Okay so you found it: the "Keep unexpected index" comes from these recent Odoo changes indeed. In v12.0, the commit was made on June 4: 
    https://github.com/odoo/odoo/commit/13f02a60c8706b808a57535ac9648a1b0c0741a9
    and the same day for OCB:

    I didn't have it in my source and it wasn't indexed in odoo/odoo that's why I didn't find it with grep.

    Now In Github it seems these commits are from June 4 and this is also why I didn't suspect this as we have builds much later than this date passing normally.
    But looking in this page it's actually clear that it was pushed by Robodoo 3 days ago: 

    So now I guess we should work on 2 fronts:
    1. do the Odoo SA Github dance to tell Odoo SA their commit creates problems. But this could take months before being heard (I'm optimistic)...
    2. hack a palliative fix in Travis to avoid blocking the PR's in the meantime. I'll try that for now and update you.

    On Sun, Aug 22, 2021 at 3:22 PM Olaf Wagner <wagner@elegosoft.com> wrote:
    On 22 Aug 2021, at 18:52, Raphaël Valyi wrote:
    
    
    
    > Hello contributors,
    
    
    > since 2 or 3 days ago max, on several OCA 12.0 builds one can see logs 
    
    
    > full of "Keep unexpected index" log messages such as:
    
    
    > 2021-08-22 13:29:16,607 7203  INFO  openerp_template odoo.schema: Keep 
    
    
    > unexpected index ir_model_data_date_update_index on table 
    
    
    > ir_model_data   1024 2021-08-22 13:29:16,607 7203  INFO  
    
    
    > openerp_template odoo.schema: Keep unexpected index 
    
    
    > ir_model_data_date_init_index on table ir_model_data   1025 2021-08-22 
    
    
    > 13:29:16,608 7203  INFO  openerp_template odoo.schema: Keep unexpected 
    
    
    > index ir_model_data_create_uid_index on table ir_model_data   1026 
    
    
    > 2021-08-22 13:29:16,608 7203  INFO  openerp_template odoo.schema: Keep 
    
    
    > unexpected index ir_model_data_create_date_index on table 
    
    
    > ir_model_data   1027 2021-08-22 13:29:16,608 7203  INFO  
    
    
    > openerp_template odoo.schema: Keep unexpected index 
    
    
    > ir_model_data_write_uid_index on table ir_model_data   1028 2021-08-22 
    
    
    > 13:29:16,608 7203  INFO  openerp_template odoo.schema: Keep unexpected 
    
    
    > index ir_model_data_write_date_index on table ir_model_data
    
    It’s from this change in the ORM:
    - 
    https://github.com/odoo/odoo/commit/13f02a60c8706b808a57535ac9648a1b0c0741a9
    - 
    https://github.com/odoo/odoo/commit/b4647cbf1e483bcc42ff9962851f94c751e5eebb
    
    Must have been merged recently.
    
    I’ve encountered it in 13.0 and have disabled it locally as it was 
    spamming our
    logs, too.
    
    Olaf
    
    
    -- 
    Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com
                    Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, 
    Germany
    Geschäftsführer: Olaf Wagner | Sitz: Berlin
    Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: 
    DE163214194
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Raphaël Valyi
    Founder and consultant


    by "Raphaël Valyi" <rvalyi@akretion.com> - 10:31 - 22 Aug 2021
  • Re: Travis logs full of "INFO openerp_test odoo.schema: Keep unexpected index"
    On 22 Aug 2021, at 18:52, Raphaël Valyi wrote:
    
    
    > Hello contributors,
    
    > since 2 or 3 days ago max, on several OCA 12.0 builds one can see logs 
    
    > full of "Keep unexpected index" log messages such as:
    
    > 2021-08-22 13:29:16,607 7203  INFO  openerp_template odoo.schema: Keep 
    
    > unexpected index ir_model_data_date_update_index on table 
    
    > ir_model_data   1024 2021-08-22 13:29:16,607 7203  INFO  
    
    > openerp_template odoo.schema: Keep unexpected index 
    
    > ir_model_data_date_init_index on table ir_model_data   1025 2021-08-22 
    
    > 13:29:16,608 7203  INFO  openerp_template odoo.schema: Keep unexpected 
    
    > index ir_model_data_create_uid_index on table ir_model_data   1026 
    
    > 2021-08-22 13:29:16,608 7203  INFO  openerp_template odoo.schema: Keep 
    
    > unexpected index ir_model_data_create_date_index on table 
    
    > ir_model_data   1027 2021-08-22 13:29:16,608 7203  INFO  
    
    > openerp_template odoo.schema: Keep unexpected index 
    
    > ir_model_data_write_uid_index on table ir_model_data   1028 2021-08-22 
    
    > 13:29:16,608 7203  INFO  openerp_template odoo.schema: Keep unexpected 
    
    > index ir_model_data_write_date_index on table ir_model_data
    
    It’s from this change in the ORM:
    - 
    https://github.com/odoo/odoo/commit/13f02a60c8706b808a57535ac9648a1b0c0741a9
    - 
    https://github.com/odoo/odoo/commit/b4647cbf1e483bcc42ff9962851f94c751e5eebb
    
    Must have been merged recently.
    
    I’ve encountered it in 13.0 and have disabled it locally as it was 
    spamming our
    logs, too.
    
    Olaf
    
    -- 
    Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com
                    Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, 
    Germany
    Geschäftsführer: Olaf Wagner | Sitz: Berlin
    Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: 
    DE163214194
    

    by Olaf Wagner - 08:20 - 22 Aug 2021
  • Travis logs full of "INFO openerp_test odoo.schema: Keep unexpected index"
    Hello contributors,

    since 2 or 3 days ago max, on several OCA 12.0 builds one can see logs full of "Keep unexpected index" log messages such as:

    2021-08-22 13:29:16,607 7203 INFO openerp_template odoo.schema: Keep unexpected index ir_model_data_date_update_index on table ir_model_data
    10242021-08-22 13:29:16,607 7203 INFO openerp_template odoo.schema: Keep unexpected index ir_model_data_date_init_index on table ir_model_data
    10252021-08-22 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep unexpected index ir_model_data_create_uid_index on table ir_model_data
    10262021-08-22 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep unexpected index ir_model_data_create_date_index on table ir_model_data
    10272021-08-22 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep unexpected index ir_model_data_write_uid_index on table ir_model_data
    10282021-08-22 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep unexpected index ir_model_data_write_date_index on table ir_model_data

    --

    some examples among many:

    The strange logs are there but the build is still successful.

    The problem is that these "unexepected index" messages make the logs so verbose that the test job is killed because we are exhausting the log length quota in repos with lots of tests like OCA/l10n-brazil:
    "The job exceeded the maximum log length, and has been terminated."

    I can see no recent change in the Odoo 12.0 branch nor OCA/maintainer-quality-tools that could explain such changes. Seems there is no psycopg update either.

    Any idea how to fix this? This is blocking lot's of PR in repos such as OCA/l10n-brazil but I'm sure other repos will soon be blocked too.

    Best regards. 


    Raphaël Valyi
    Founder and consultant


    by "Raphaël Valyi" <rvalyi@akretion.com> - 06:50 - 22 Aug 2021
  • Re: /ocabot rebase and improved addons table
    Thanks!

    On Fri, 13 Aug 2021 at 10:57, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Hi folks!

    I just deployed a new version of our GitHub bot with the following new features:

    A new /ocabot rebase command (contributed by Miquel Raïch).

    An update to the README.md addons table generator to show the addons maintainers (contributed by Sylvain Le Gal).

    Have a nice day,

    -sbi

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    by Lorenzo Battistini. - 05:35 - 19 Aug 2021
  • Re: Employee contract builder in Odoo
    Yes agreement_legal should do the work. We use this all the time.

    On Wed, Aug 18, 2021, 23:57 Daniel Reis <dreis@opensourceintegrators.com> wrote:
    Yes, the oca/contract "agreement" module might do what you want.
    Have a look at https://github.com/OCA/contract/tree/12.0/agreement_legal

    Thanks
    Daniel

    On 18/08/21 17:37, Bruno Joliveau wrote:
    Hi Tom,

    I don't remember ever having seen such a module around HR.

    We made a "Clausier" in a very old version of odoo (v6) for notaries and lawyers, but it would have too much effort to adapt it to the current version.

    Concern your need there could be a base with agreement modules on https://github.com/OCA/contract

    Have a nice day!

    Bruno Joliveau - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedin youtube custom-icon twitter


    Le mer. 18 août 2021 à 12:22, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :
    Hi OCA,
    
    A customer has a need for a solution that can allow HR users to 'build' 
    an employee contract by selecting texts from a predefined list of HTML 
    snippets.
    
    For example:
    
    Section A:
    
    - Clause type A (select from list)
    - Clause type A (select from list)
    - Clause type A (select from list)
    
    Section B:
    
    - Clause type B (select from list)
    
    The clauses should be poweruser-editable, translatable HTML snippets in 
    which also placeholders can be used such as in Odoo email templates: 
    {{employee.name}} and the like.
    
    It's possible to custom-build this, but is there anyone who has already 
    seen something like this in action? I know some legal firms which had 
    something like this custom-built in order to serve their customers 
    quicker and sell them auto-generated contracts based on an online survey 
    that the customer has to fill, thereby earning good money with very 
    little work; but I haven't seen it in Odoo yet.
    
    -Tom
    
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Kitti Upariphutthiphong - 09:05 - 19 Aug 2021
  • Re: Travis .pot push issue
    Thanks for your help Stéphane!

    On Wed, Aug 18, 2021 at 6:52 PM Daniel Reis <dreis@opensourceintegrators.com> wrote:
    Five star service!
    Thank you Stephane.
    
    
    On 18/08/21 17:32, Stéphane Bidoul wrote:
    
    
    > Hi,
    
    
    >
    
    
    > This afternoon you may have noticed merge commands failing due to a 
    
    
    > token error when Travis tried to push the generated .pot files back to 
    
    
    > GitHub.
    
    
    >
    
    
    > For some reason our token had become invalid and a new one had to be 
    
    
    > generated and pushed to the config of all repos... which was something 
    
    
    > I had hoped to avoid since that solution was put in place.
    
    
    >
    
    
    > It is now resolved. Let me know if there are any remaining issues.
    
    
    >
    
    
    > Best regards,
    
    
    >
    
    
    > -sbi
    
    
    >
    
    
    > _______________________________________________
    
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    
    > Post to: mailto:contributors@odoo-community.org
    
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    
    >
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

    by Simone Orsi - 07:25 - 18 Aug 2021
  • Re: Employee contract builder in Odoo
    Yes, the oca/contract "agreement" module might do what you want.
    Have a look at https://github.com/OCA/contract/tree/12.0/agreement_legal

    Thanks
    Daniel

    On 18/08/21 17:37, Bruno Joliveau wrote:
    Hi Tom,

    I don't remember ever having seen such a module around HR.

    We made a "Clausier" in a very old version of odoo (v6) for notaries and lawyers, but it would have too much effort to adapt it to the current version.

    Concern your need there could be a base with agreement modules on https://github.com/OCA/contract

    Have a nice day!

    Bruno Joliveau - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedin youtube custom-icon twitter


    Le mer. 18 août 2021 à 12:22, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :
    Hi OCA,
    
    A customer has a need for a solution that can allow HR users to 'build' 
    an employee contract by selecting texts from a predefined list of HTML 
    snippets.
    
    For example:
    
    Section A:
    
    - Clause type A (select from list)
    - Clause type A (select from list)
    - Clause type A (select from list)
    
    Section B:
    
    - Clause type B (select from list)
    
    The clauses should be poweruser-editable, translatable HTML snippets in 
    which also placeholders can be used such as in Odoo email templates: 
    {{employee.name}} and the like.
    
    It's possible to custom-build this, but is there anyone who has already 
    seen something like this in action? I know some legal firms which had 
    something like this custom-built in order to serve their customers 
    quicker and sell them auto-generated contracts based on an online survey 
    that the customer has to fill, thereby earning good money with very 
    little work; but I haven't seen it in Odoo yet.
    
    -Tom
    
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    by Daniel Reis - 06:56 - 18 Aug 2021
  • Re: Travis .pot push issue
    Five star service!
    Thank you Stephane.
    
    
    On 18/08/21 17:32, Stéphane Bidoul wrote:
    
    > Hi,
    
    >
    
    > This afternoon you may have noticed merge commands failing due to a 
    
    > token error when Travis tried to push the generated .pot files back to 
    
    > GitHub.
    
    >
    
    > For some reason our token had become invalid and a new one had to be 
    
    > generated and pushed to the config of all repos... which was something 
    
    > I had hoped to avoid since that solution was put in place.
    
    >
    
    > It is now resolved. Let me know if there are any remaining issues.
    
    >
    
    > Best regards,
    
    >
    
    > -sbi
    
    >
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    >
    
    

    by Daniel Reis - 06:50 - 18 Aug 2021
  • Re: Travis .pot push issue
    Thanks for doing the nasty maintenance work.

    Regards.

    El mié., 18 ago. 2021 18:32, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:
    Hi,

    This afternoon you may have noticed merge commands failing due to a token error when Travis tried to push the generated .pot files back to GitHub.

    For some reason our token had become invalid and a new one had to be generated and pushed to the config of all repos... which was something I had hoped to avoid since that solution was put in place.

    It is now resolved. Let me know if there are any remaining issues.

    Best regards,

    -sbi

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Pedro M. Baeza - 06:45 - 18 Aug 2021
  • Re: Employee contract builder in Odoo
    Hi Tom,

    I don't remember ever having seen such a module around HR.

    We made a "Clausier" in a very old version of odoo (v6) for notaries and lawyers, but it would have too much effort to adapt it to the current version.

    Concern your need there could be a base with agreement modules on https://github.com/OCA/contract

    Have a nice day!
    Bruno Joliveau - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter


    Le mer. 18 août 2021 à 12:22, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :
    Hi OCA,
    
    A customer has a need for a solution that can allow HR users to 'build' 
    an employee contract by selecting texts from a predefined list of HTML 
    snippets.
    
    For example:
    
    Section A:
    
    - Clause type A (select from list)
    - Clause type A (select from list)
    - Clause type A (select from list)
    
    Section B:
    
    - Clause type B (select from list)
    
    The clauses should be poweruser-editable, translatable HTML snippets in 
    which also placeholders can be used such as in Odoo email templates: 
    {{employee.name}} and the like.
    
    It's possible to custom-build this, but is there anyone who has already 
    seen something like this in action? I know some legal firms which had 
    something like this custom-built in order to serve their customers 
    quicker and sell them auto-generated contracts based on an online survey 
    that the customer has to fill, thereby earning good money with very 
    little work; but I haven't seen it in Odoo yet.
    
    -Tom
    
    
    

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Bruno Joliveau - 06:36 - 18 Aug 2021
  • Travis .pot push issue
    Hi,

    This afternoon you may have noticed merge commands failing due to a token error when Travis tried to push the generated .pot files back to GitHub.

    For some reason our token had become invalid and a new one had to be generated and pushed to the config of all repos... which was something I had hoped to avoid since that solution was put in place.

    It is now resolved. Let me know if there are any remaining issues.

    Best regards,

    -sbi

    by Stéphane Bidoul - 06:31 - 18 Aug 2021
  • Employee contract builder in Odoo
    Hi OCA,
    
    A customer has a need for a solution that can allow HR users to 'build' 
    an employee contract by selecting texts from a predefined list of HTML 
    snippets.
    
    For example:
    
    Section A:
    
    - Clause type A (select from list)
    - Clause type A (select from list)
    - Clause type A (select from list)
    
    Section B:
    
    - Clause type B (select from list)
    
    The clauses should be poweruser-editable, translatable HTML snippets in 
    which also placeholders can be used such as in Odoo email templates: 
    {{employee.name}} and the like.
    
    It's possible to custom-build this, but is there anyone who has already 
    seen something like this in action? I know some legal firms which had 
    something like this custom-built in order to serve their customers 
    quicker and sell them auto-generated contracts based on an online survey 
    that the customer has to fill, thereby earning good money with very 
    little work; but I haven't seen it in Odoo yet.
    
    -Tom
    
    
    

    by Tom Blauwendraat - 06:21 - 18 Aug 2021
  • Re: /ocabot rebase and improved addons table
    Yes, indeed any improvement is welcome.

    Regards.

    by Pedro M. Baeza - 12:05 - 13 Aug 2021
  • Re: /ocabot rebase and improved addons table
    OK ! thanks for the info. I didn't know.

    Well, we can hope that such github limitation will be dropped.

    anyway, I think its a good step forward, because it allows to rebase many PRs, and I think that Acsone, ForgeFlow, Tecnativa members teams are quite reactive when we ask to rebase.




    Sylvain LE GAL - Twitter
    GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
    Site Web | FramaSphere | Facebook
    3 Grande rue des Feuillants, 69001 Lyon
    Standard : (+33) 09.72.32.33.17
    Service Informatique : (+33) 09.73.79.64.40
    Astreinte Informatique : (+33) 06.81.85.61.43
    Member of the OCA (Odoo Community Association)


    Le ven. 13 août 2021 à 11:52, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    Sylvain, it's not something that can be decided when the branch from which you make the pull request belongs to an organization instead of an individual user. GitHub doesn't allow you to push to that branches even if the pull request has that check marked. I don't understand such limitation, but it's there, and most of the regular contributors (Acsone, ForgeFlow, Tecnativa, etc) use this technique for allowing anyone in the team to handle the PR.

    I understand then that this command can't be used in such PRs.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Sylvain LE GAL - 12:00 - 13 Aug 2021
  • Re: /ocabot rebase and improved addons table
    Sylvain, it's not something that can be decided when the branch from which you make the pull request belongs to an organization instead of an individual user. GitHub doesn't allow you to push to that branches even if the pull request has that check marked. I don't understand such limitation, but it's there, and most of the regular contributors (Acsone, ForgeFlow, Tecnativa, etc) use this technique for allowing anyone in the team to handle the PR.

    I understand then that this command can't be used in such PRs.

    Regards.

    by Pedro M. Baeza - 11:50 - 13 Aug 2021
  • Re: /ocabot rebase and improved addons table
    > I have the same question as Pedro has. I suppose the command will do the rebase only if the maintainer is allowed to push to the forked repo.

    Indeed, but this is the default when creating new PR. And if the developper that makes the PR disable that feature, we should not by pass that.

    see below :

    image.png



    Sylvain LE GAL - Twitter
    GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)
    Site Web | FramaSphere | Facebook
    3 Grande rue des Feuillants, 69001 Lyon
    Standard : (+33) 09.72.32.33.17
    Service Informatique : (+33) 09.73.79.64.40
    Astreinte Informatique : (+33) 06.81.85.61.43
    Member of the OCA (Odoo Community Association)


    Le ven. 13 août 2021 à 11:32, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :
    Awesome! Thank you Miquel, Stéphane.

    I have the same question as Pedro has. I suppose the command will do the rebase only if the maintainer is allowed to push to the forked repo.

    Regards.

    On Fri, 13 Aug 2021 at 11:12, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
    Great improvements, thanks!

    I wonder if the rebase command will work on organization branches, where by default maintainers can't update the pull request branch.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Sylvain LE GAL - 11:41 - 13 Aug 2021
  • Re: /ocabot rebase and improved addons table
    Awesome! Thank you Miquel, Stéphane.

    I have the same question as Pedro has. I suppose the command will do the rebase only if the maintainer is allowed to push to the forked repo.

    Regards.

    On Fri, 13 Aug 2021 at 11:12, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
    Great improvements, thanks!

    I wonder if the rebase command will work on organization branches, where by default maintainers can't update the pull request branch.

    Regards.

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Aarón Henríquez - 11:31 - 13 Aug 2021
  • Re: /ocabot rebase and improved addons table
    Great improvements, thanks!

    I wonder if the rebase command will work on organization branches, where by default maintainers can't update the pull request branch.

    Regards.

    by Pedro M. Baeza - 11:11 - 13 Aug 2021
  • Re: /ocabot rebase and improved addons table
    Great!

    Maybe a README improvement for that should be the explanation of what happens when rebase is failing (some may think it will be pushed with crap).

    Thanks

    On Fri, Aug 13, 2021 at 10:57 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Hi folks!

    I just deployed a new version of our GitHub bot with the following new features:

    A new /ocabot rebase command (contributed by Miquel Raïch).

    An update to the README.md addons table generator to show the addons maintainers (contributed by Sylvain Le Gal).

    Have a nice day,

    -sbi

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

    by Denis Roussel - 11:05 - 13 Aug 2021
  • /ocabot rebase and improved addons table
    Hi folks!

    I just deployed a new version of our GitHub bot with the following new features:

    A new /ocabot rebase command (contributed by Miquel Raïch).

    An update to the README.md addons table generator to show the addons maintainers (contributed by Sylvain Le Gal).

    Have a nice day,

    -sbi

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    by Stéphane Bidoul - 10:56 - 13 Aug 2021