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

portalicious: registrations table component #6104

Merged
merged 1 commit into from
Nov 14, 2024

Conversation

aberonni
Copy link
Contributor

@aberonni aberonni commented Nov 14, 2024

AB#31335

Moving the registrations table into a separate component so that it can easily be re-used by the "do payment" flow

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have added tests wherever relevant
  • I have made sure that all automated checks pass before requesting a review
  • I do not need any deviation from our PR guidelines

AB#31335

Moving the registrations table into a separate component so that it can easily be re-used by the "do payment" flow
@aberonni aberonni added the portalicious Changes related to the portalicious release label Nov 14, 2024
@aberonni aberonni marked this pull request as ready for review November 14, 2024 11:16
@aberonni aberonni enabled auto-merge (squash) November 14, 2024 11:16
@aberonni aberonni merged commit 2a103ee into main Nov 14, 2024
5 checks passed
@aberonni aberonni deleted the aberonni/portalicious-registrations-table-component branch November 14, 2024 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
portalicious Changes related to the portalicious release
Development

Successfully merging this pull request may close these issues.

2 participants