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 chore: update 'status' translation #6407

Merged

Conversation

PeterSmallenbroek
Copy link
Contributor

@PeterSmallenbroek PeterSmallenbroek commented Jan 21, 2025

AB#32822

Describe your changes

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

Portalicious preview deployment

https://lively-river-04adce503-6407.westeurope.5.azurestaticapps.net

@PeterSmallenbroek PeterSmallenbroek added the portalicious [DEPRECATED] Changes related to the Portalicious release label Jan 21, 2025
@PeterSmallenbroek PeterSmallenbroek changed the title chore: update 'status' translation Portalicious chore: update 'status' translation Jan 21, 2025
@PeterSmallenbroek PeterSmallenbroek enabled auto-merge (squash) January 21, 2025 12:23
@PeterSmallenbroek PeterSmallenbroek force-pushed the chore.portalicious-update-status-translation branch from 9764aa2 to 6374831 Compare January 21, 2025 12:44
@PeterSmallenbroek PeterSmallenbroek force-pushed the chore.portalicious-update-status-translation branch from 6374831 to 7aac928 Compare January 21, 2025 14:58
@PeterSmallenbroek PeterSmallenbroek merged commit ad9b3f2 into main Jan 21, 2025
6 checks passed
@PeterSmallenbroek PeterSmallenbroek deleted the chore.portalicious-update-status-translation branch January 21, 2025 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
portalicious [DEPRECATED] Changes related to the Portalicious release
Development

Successfully merging this pull request may close these issues.

2 participants