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

[15.0][MIG] iot_rule #71

Merged
merged 7 commits into from
Jun 26, 2023
Merged

[15.0][MIG] iot_rule #71

merged 7 commits into from
Jun 26, 2023

Conversation

AaronHForgeFlow
Copy link
Contributor

@AaronHForgeFlow AaronHForgeFlow force-pushed the 15-mig-iot_rule branch 3 times, most recently from 57a09c4 to 0c27d13 Compare December 5, 2022 17:04
@AaronHForgeFlow AaronHForgeFlow changed the title [15.0][MIG] iot_rule and iot_key_employee_rfid [15.0][MIG] iot_rule Dec 5, 2022
Copy link
Member

@etobella etobella left a comment

Choose a reason for hiding this comment

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

/ocabot migration iot_rule

@OCA-git-bot OCA-git-bot added this to the 15.0 milestone Feb 23, 2023
@OCA-git-bot OCA-git-bot mentioned this pull request Feb 23, 2023
2 tasks
@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 25, 2023
@AaronHForgeFlow
Copy link
Contributor Author

@etobella could you please remove the stale label?

@etobella etobella added no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Jun 26, 2023
@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). 🤖

@etobella
Copy link
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 15.0-ocabot-merge-pr-71-by-etobella-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 2ba64a1 into OCA:15.0 Jun 26, 2023
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 233c6f7. 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
Labels
approved merged 🎉 no stale Use this label to prevent the automated stale action from closing this PR/Issue. ready to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants