Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to merge envs properly? Getting my team-provider.json overwritten. #13917

Open
christiansaavedra opened this issue Sep 9, 2024 · 1 comment
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question

Comments

@christiansaavedra
Copy link

Amplify CLI Version

12.12.6

Question

Hello, I've been making changes in git branch develop and amplify env develop. I've pushed them both
Now, to merge these changes to the superior branch and env (staging), I've followed these instructions: here

So, I did git checkout staging, git pull, amplify pull staging. However, when i run 'git merge develop', my team-provider.json gets overriden (the only env appearing is the develop one, the staging is completely empited).

I'm wondering what i am doing wrong and what are the correct procedures to succesfully merge my develop env in the staigng one.

@christiansaavedra christiansaavedra added pending-triage Issue is pending triage question General question labels Sep 9, 2024
@ykethan
Copy link
Member

ykethan commented Sep 18, 2024

Hey @christiansaavedra, the team-provider-info.json contains the env information and metadata for all environments. Is the staging branch built of the main branch?
If the staging branch is build of the main the team provider should contain the main branch record as well. When git merging you will need to ensure the team provider is appended rather overridden.

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question
Projects
None yet
Development

No branches or pull requests

2 participants