For bootstrapping a startup, depending on the business requirement, one of the best tech stack can be Amplify + NextJs. Now, when working with Amplify + NextJs MonoRepo, this is how you should <a target="_blank" href="https://jawaddev.hashnode.dev/how-to-push-your-lambda-function-into-amplify-nextjs-monorepo">push</a> your changes, still there can be instances where you're faced with a git merge error
<ol>
<li>Fetch remote staging into local staging, while staying in your branch</li>
</ol>
<pre><code class="lang-jsx">git fetch origin staging:staging
</code></pre>
<ol>
<li>Merge local staging into development branch</li>
<li>Resolve git conflict by accepting changes of your branch if you made changes to those files, and for the rest of them you didn’t change just accept staging version. </li>
<li>Amplify pull</li>
<li>Commit &amp; push team-provider-info.json &amp; backend-config.json files, since they now contain the latest amplify configs.</li>
</ol>

For bootstrapping a startup, depending on the business requirement, one of the best tech stack can be Amplify + NextJs. Now, when working with Amplify + NextJs MonoRepo, this is how you should [push](https://jawaddev.hashnode.dev/how-to-push-your-lambda-function-into-amplify-nextjs-monorepo) your changes, still there can be instances where you're faced with a git merge error

1. Fetch remote staging into local staging, while staying in your branch

```jsx
git fetch origin staging:staging
```

1. Merge local staging into development branch
2. Resolve git conflict by accepting changes of your branch if you made changes to those files, and for the rest of them you didn’t change just accept staging version. 
3. Amplify pull
4. Commit & push **team-provider-info.json** & **backend-config.json** files, since they now contain the latest amplify configs.

How to resolve merge conflict in Amplify + Next MonoRepo