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

[16.0][MIG] partner_equal_ref_barcode: Migration to 16.0 #2535

Closed

Conversation

unaiberis
Copy link
Contributor

No description provided.

@unaiberis unaiberis force-pushed the 16.0-mig-partner_equal_ref_barcode branch 3 times, most recently from e780e9c to 651bbde Compare July 8, 2024 08:41
anajuaristi
anajuaristi previously approved these changes Jul 15, 2024
@unaiberis unaiberis force-pushed the 16.0-mig-partner_equal_ref_barcode branch 2 times, most recently from d13f96d to b40734f Compare July 15, 2024 15:03
anajuaristi
anajuaristi previously approved these changes Jul 15, 2024
@unaiberis unaiberis force-pushed the 16.0-mig-partner_equal_ref_barcode branch from e2eedad to ec67589 Compare July 15, 2024 15:10
anajuaristi
anajuaristi previously approved these changes Jul 15, 2024
@unaiberis unaiberis force-pushed the 16.0-mig-partner_equal_ref_barcode branch 2 times, most recently from 9078d66 to 336d4c3 Compare July 15, 2024 15:15
anajuaristi
anajuaristi previously approved these changes Jul 16, 2024
@unaiberis unaiberis force-pushed the 16.0-mig-partner_equal_ref_barcode branch from 2b01676 to ad4a79e Compare July 16, 2024 07:42
@unaiberis unaiberis force-pushed the 16.0-mig-partner_equal_ref_barcode branch from ad4a79e to b24edae Compare July 16, 2024 07:46
@unaiberis unaiberis force-pushed the 16.0-mig-partner_equal_ref_barcode branch from bc95fdb to 98a841f Compare July 16, 2024 07:48
@unaiberis unaiberis closed this Jul 16, 2024
@unaiberis unaiberis deleted the 16.0-mig-partner_equal_ref_barcode branch July 16, 2024 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants