Feature(point-of-sale): AB testing #235
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JustSamuel
force-pushed
the
feature/ab-testing
branch
from
4208499 to
269d43f
Compare
JustSamuel
force-pushed
the
feature/ab-testing
branch
from
269d43f to
b52f3c6
Compare
…/ab-testing # Conflicts: # .github/workflows/point-of-sale-docker-ab.yml
SuperVK
requested changes
Jun 24, 2024
SuperVK
approved these changes
Jun 24, 2024
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds an implementation of AB testing using a separate GitHub action. The idea of the action is that it builds the development branch with the production env variables such that it can be used next to the main branch side by side.
This is nice for the point-of-sale as our develop branch will automagically become a canary release.
You can also view the tag and branch that is running in the bottom right of the login screen:
Related issues/external references
Types of changes