{"push_id":1473677176,"size":6,"distinct_size":0,"ref":"refs/heads/10.0","head":"634fb9f390e12a37e6bf29e1edd95759b2fc468a","before":"b21d1ae98e2d48c308b1015bddc6b457aaad3a87","commits":[{"sha":"22fb76a002d7bc8f3f57ddbbed2006d2176cdff2","author":{"name":"Goffin Simon","email":"27fb2926b4ed71baf246c49114acdb9ea83f3eb6@odoo.com"},"message":"[FIX] mrp: field resource_type in mrp.workcenter tree view\n\nThe field resource_type in mrp.workcenter tree view must be invisible because\nthis field was not available in the form view before f9f4bba\n\nAdding resource_type in the form view had no business case.\n\nopw:698183","distinct":false,"url":"https://api.github.com/repos/acsone/odoo/commits/22fb76a002d7bc8f3f57ddbbed2006d2176cdff2"},{"sha":"bdbda19b6df51e367237f002d3aea71dee540629","author":{"name":"Nicolas Martinelli","email":"76fd54f3784bbe4be7fb6e989b36e7f74a3407b8@odoo.com"},"message":"[FIX] stock: prevent concurrent procurement creation\n\nWhen the user clicks on \"Run Reordering Rules\", it might create\nprocurements. However, the cron \"Run mrp scheduler\" will also create\nprocurements and might already be running in the background. Therefore,\nwe need to make sure that both actions don't run concurrently.\n\nNote that the same check is done for the wizard \"Run Schedulers\".\n\nopw-695607","distinct":false,"url":"https://api.github.com/repos/acsone/odoo/commits/bdbda19b6df51e367237f002d3aea71dee540629"},{"sha":"562f141ffc13adcaa23c694dfba213a890f6e1ef","author":{"name":"Nicolas Martinelli","email":"76fd54f3784bbe4be7fb6e989b36e7f74a3407b8@odoo.com"},"message":"[FIX] stock: hide \"Run Reordering Rules\"\n\nThis should only be accessible in debug mode, since it is already\npossible to run the schedulers (with a simialr effect) manually.","distinct":false,"url":"https://api.github.com/repos/acsone/odoo/commits/562f141ffc13adcaa23c694dfba213a890f6e1ef"},{"sha":"88d7e7f646a2b2bf2bda3c83b37ec18190686a5c","author":{"name":"Nicolas Lempereur","email":"20b6a29c46d1a38278b1511d2765b429bce35dfb@odoo.com"},"message":"Revert \"[FIX] mail: livechat escaping\"\n\nThis reverts commit 1c60a631df8b42b90973e117eae5d510fcc0f223.\n\nThe fix was done to conciliate 83956d4 and ff56304f5 but ff56304f5 was\nforward-ported erroneously and introduced other issues.\n\nopw-702410","distinct":false,"url":"https://api.github.com/repos/acsone/odoo/commits/88d7e7f646a2b2bf2bda3c83b37ec18190686a5c"},{"sha":"46f84b02845ab5d99a10bb920122df9663615f33","author":{"name":"Nicolas Lempereur","email":"20b6a29c46d1a38278b1511d2765b429bce35dfb@odoo.com"},"message":"[FIX] mail: linkify livechat message so frontend has them\n\nIn ff56304f58c a solution was tried to have message posted from\nbackend livechat linkified for visitor in frontend. This was\nforward-ported when it should not have been and introduced issues\nincluding:\n\n- `href=\"{link}\"` would become `href=\"<a href=\"{link}\">{link}</a>\"`\n\n- if html entities such as the ones for U+00A0, and entities <, >,\n  ', \" or ` were next to the link, the entity would be linkified\n  too (up to the ;)\n\nThis happen because utils.linkify function is to be used with text\ncontent and not html which was the case in this instance.\n\nopw-693457\nopw-702410","distinct":false,"url":"https://api.github.com/repos/acsone/odoo/commits/46f84b02845ab5d99a10bb920122df9663615f33"},{"sha":"634fb9f390e12a37e6bf29e1edd95759b2fc468a","author":{"name":"Nicolas Martinelli","email":"76fd54f3784bbe4be7fb6e989b36e7f74a3407b8@odoo.com"},"message":"[FIX] purchase: purchase count\n\nThe field `purchase_count` is described as '# Purchases' (which is an\ninteger), so the user should expect the number of POs associated to the\nproduct, not the quantity ordered as it is the case before this commit.\n\nopw-697815","distinct":false,"url":"https://api.github.com/repos/acsone/odoo/commits/634fb9f390e12a37e6bf29e1edd95759b2fc468a"}]}
{"actor":{"display_login":"acsone-git-bot"}}