feat: add support for email server to acceptance workflow#58
Merged
DeepDiver1975 merged 1 commit intomainfrom Apr 28, 2026
Merged
feat: add support for email server to acceptance workflow#58DeepDiver1975 merged 1 commit intomainfrom
DeepDiver1975 merged 1 commit intomainfrom
Conversation
phil-davis
force-pushed
the
add-email-to-acceptance
branch
from
9ea82fc to
2ed1c46
Compare
DeepDiver1975
approved these changes
Apr 28, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds an option to start the https://hub.docker.com/r/inbucket/inbucket email server for use by the acceptance tests.
To get the email server, when calling the reusable workflow put:
The workflow will start the "inbucket" docker image running directly on "localhost", and define env var
EMAIL_HOST=localhostThe acceptance test code already expects an "inbucket" mail server, and knows how to access it's port(s) to check mail etc.
(this is how it worked already in drone)
I added a test pipeline to run the notifications app API tests with an email server (which it needs, it checks notification emails). This will validate that the workflow works.