-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[16.0] [MIG] sale_timesheet_project_manual #2555
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
base: 16.0
Are you sure you want to change the base?
[16.0] [MIG] sale_timesheet_project_manual #2555
Conversation
/ocabot migration sale_timesheet_project_manual |
4fa7c87
to
ee87655
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code review - LGTM
ee87655
to
2d97252
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functional review LGTM.
b1c1397
to
df562a9
Compare
/ocabot migration sale_timesheet_project_manual |
/ocabot rebase |
@rafaelbn The rebase process failed, because command
|
Trying that runbot works! |
df562a9
to
1fe404f
Compare
@rafaelbn Hi, I made a rebase, i hope that will trigger a new runboat |
@FrancoMaxime Could you rebase ? |
… a draft sale.order, the button linked to projects should be available for this state
1fe404f
to
58f6535
Compare
This PR has the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @FrancoMaxime , thank you for your contribution! Please check the migration checklist and squash administrative commits (if any) with the previous commit for reducing commit noise
@ivs-cetmix I don't see administrative commits that should be squashed. Moreover, this is not mandatory before merge. Please update your review |
@rousseldenis here it is. And because this step is listed in the "Tasks to do in the migration" it's reasonable to consider it to be a mandatory one. |
I never block migration for that reason. As IMHO, that changes the original commit stack. |
@rousseldenis those are the migration requirements and they must be followed. You can open a discussion in the maintainer-tools if you think this should be changed. |
|
No description provided.