Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[13.0][MIG] stock_no_negative #597

Closed
wants to merge 26 commits into from

Conversation

qdelcourte
Copy link
Contributor

No description provided.

alexis-via and others added 25 commits December 19, 2019 09:54
Currently translated at 50.0% (4 of 8 strings)

Translation: stock-logistics-workflow-11.0/stock-logistics-workflow-11.0-stock_no_negative
Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-workflow-11-0/stock-logistics-workflow-11-0-stock_no_negative/ar/
For example, when you install *delivery* along with this one
Updated by Update PO files to match POT (msgmerge) hook in Weblate.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: stock-logistics-workflow-12.0/stock-logistics-workflow-12.0-stock_no_negative
Translate-URL: https://translation.odoo-community.org/projects/stock-logistics-workflow-12-0/stock-logistics-workflow-12-0-stock_no_negative/
@oca-clabot
Copy link

Hey @qdelcourte, thank you for your Pull Request.

It looks like some users haven't signed our Contributor License Agreement, yet.
You can read and sign our full Contributor License Agreement here: http://odoo-community.org/page/cla
Here is a list of the users:

Appreciation of efforts,
OCA CLAbot

@qdelcourte qdelcourte changed the title [13.0][MIG] stock no negative [13.0][MIG] stock_no_negative Dec 19, 2019
@qdelcourte qdelcourte mentioned this pull request Dec 19, 2019
36 tasks
@pedrobaeza pedrobaeza added this to the 13.0 milestone Dec 19, 2019
Comment on lines +1 to +4
11.0.1.1.0 (2018-12-13)
~~~~~~~~~~~~~~~~~~~~~~~

* Add the ability to allow negative stock for individual stock locations.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please edit HISTORY.rst up to date.

Comment on lines +1 to +6
* Alexis de Lattre <[email protected]>
* Eficent Business and IT Consulting Services S.L. <[email protected]>
* Jordi Ballester
* Serpent Consulting Services Pvt. Ltd. <[email protected]>
* Tecnativa <https://www.tecnativa.com>
* Pedro M. Baeza
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add you add a contributor.

Copy link
Contributor

@rousseldenis rousseldenis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review

@rousseldenis
Copy link
Contributor

@qdelcourte Please use pre-commit to fix error.

@ps-tubtim
Copy link
Member

@qdelcourte Please generate new README.rst after edit .rst file with https://github.com/OCA/maintainer-tools.

Copy link
Contributor

@jesus01x jesus01x left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

functional and technical review.

@kittiu
Copy link
Member

kittiu commented Jan 10, 2020

@ps-tubtim i think generate readme is not necessary. Ocabot will do it when merge.

Copy link
Contributor

@rousseldenis rousseldenis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review

Copy link
Contributor

@alan196 alan196 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functional and technical review 👍

You only need to use pre-commit to fix travis

@alan196
Copy link
Contributor

alan196 commented Feb 12, 2020

@qdelcourte will you continue working with this PR?

@LoisRForgeFlow
Copy link
Contributor

Well, I guess travis still need to be attended...

@pedrobaeza
Copy link
Member

Superseded by #666

@pedrobaeza pedrobaeza closed this Jun 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.