Move the Amplify config into version control #304
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
Move the Amplify configuration file into version control, rather than having it only in the AWS management console. For now it doesn't use node 18.17.1, but rather the default version, so it will fail to build - but it's still progress.
Ensure that the frontend CI workflow uses the correct node version.
iamlogand
added
infrastructure
iamlogand
force-pushed
the
fix/amplify-config-in-version-control
branch
from
a1bfe58 to
5510a83
Compare
Move the amplify configuration file into the root because apparently Amplify can't detect configurations in other folders - weird but looks like my hands are tied.
iamlogand
force-pushed
the
fix/amplify-config-in-version-control
branch
from
5510a83 to
af47a9a
Compare
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.
Move the Amplify configuration file into version control, rather than having it only in the AWS management console. For now it doesn't use node 18.17.1, but rather the default version, so it will fail to build - but it's still progress.