chore: moving submodule to silverback-template repo #1448
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
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.
Package(s) involved
silverback_gatsbyDescription of changes
Remove OAuth submodule.
Motivation and context
It's not the right repo as its sole responsibility is to create a Consumer so it's a
silverback-templatespecific task for the authentication feature initialization.There shouldn't be any usage of this module yet as this change is related to AmazeeLabs/silverback-template#86 so it should be safe to delete (instead of keeping an empty module for BC).
Related Issue(s)
https://amazeelabs.atlassian.net/browse/SLB-176
How has this been tested?
Manually.