This repository has been archived by the owner on Oct 14, 2022. It is now read-only.
chore(sync): initial setup of fake API file sync #22
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
This was referenced May 18, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does it do
These changes will allow us to change the fake database file anywhere in our codebase while keeping it synced with other repositories.
Usage
Change either the
db.jsonorroutes.jsonfile and PRs will be opened in the other repositories automatically by @dalbitresb12-bot.Why is it needed
We'll be able to use
json-serverindependently in each project, while keeping the fake database in sync.Related issue(s)/PR(s)