Skip to content

[18.0][MIG] project_scrum: Migration to 18.0 #1509

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

Merged
merged 9 commits into from
May 28, 2025

Conversation

ByteMeAsap
Copy link
Contributor

No description provided.

@ByteMeAsap ByteMeAsap changed the title [18.0][MIG] project scrum: Migration to 18.0 [18.0][MIG] project_scrum: Migration to 18.0 May 20, 2025
@ByteMeAsap ByteMeAsap force-pushed the 18.0-mig-project_scrum branch from 225f19d to 8522832 Compare May 20, 2025 04:49
Copy link
Contributor

@carlos-lopez-tecnativa carlos-lopez-tecnativa 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

TT54671

@ByteMeAsap ByteMeAsap force-pushed the 18.0-mig-project_scrum branch from 8522832 to 814c91c Compare May 21, 2025 09:13
@ByteMeAsap ByteMeAsap force-pushed the 18.0-mig-project_scrum branch 2 times, most recently from c2b4a8e to b04c8af Compare May 21, 2025 13:06
Copy link
Contributor

@carlos-lopez-tecnativa carlos-lopez-tecnativa left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for the changes
Non-blocking comment, just a few minor changes to improve the UX.
@pedrobaeza @victoralmau could you please review this?

@ByteMeAsap ByteMeAsap force-pushed the 18.0-mig-project_scrum branch 2 times, most recently from 8a13043 to d9bf26e Compare May 22, 2025 13:35
@ByteMeAsap ByteMeAsap force-pushed the 18.0-mig-project_scrum branch from d9bf26e to d7abdf9 Compare May 23, 2025 10:21
Update as per suggestions
@ByteMeAsap ByteMeAsap force-pushed the 18.0-mig-project_scrum branch from d7abdf9 to b01f1a9 Compare May 28, 2025 05:55
Copy link
Contributor

@carlos-lopez-tecnativa carlos-lopez-tecnativa left a comment

Choose a reason for hiding this comment

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

@pedrobaeza
Copy link
Member

/ocabot migration project_scrum

@OCA-git-bot OCA-git-bot added this to the 18.0 milestone May 28, 2025
@OCA-git-bot OCA-git-bot mentioned this pull request May 28, 2025
30 tasks
Copy link
Member

@pedrobaeza pedrobaeza left a comment

Choose a reason for hiding this comment

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

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

On my way to merge this fine PR!
Prepared branch 18.0-ocabot-merge-pr-1509-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@OCA-git-bot OCA-git-bot merged commit f43b516 into OCA:18.0 May 28, 2025
7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 406cfd8. Thanks a lot for contributing to OCA. ❤️

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.

7 participants