Adding a new service documentation #73
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
Adding a story about how to add new services. This will help guide the devs as we add new services to Jemison.
selfdanielj
reviewed
Jan 6, 2025
IsabelLaurenceau
approved these changes
Jan 10, 2025
jadudm
commented
Jan 14, 2025
IsabelLaurenceau
approved these changes
Jan 14, 2025
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.
PRs at this point do not yet have a full guide template, and are against a system that is not yet production-ready.
This commit is documentation only. It moves some pieces around, and most importantly, adds a document that describes how to add a new service. It is reasonably complete, having been guided by the bringing together of a new service (
e2e), which could provide a starting point for a local/in-stack, repeatable path to end-to-end tests. That service is not complete, but standing up the shell/boilerplate guided this documentation.