Update the Codebase

Updating your NativeExpress codebase to the latest version is generally possible, but it's important to note that with each change you make to your application, it may become more challenging to update your code base. This is because you're essentially rebasing your code on top of the latest NativeExpress code. You'll need to resolve merge conflicts and be careful not to overwrite your own custom code.

Before You Update

Before you update your code base, ensure your git repository is clean and that you have no uncommitted changes.

Add the NativeExpress Repository as a Remote

To update your code base, you need to add the NativeExpress repository as a remote to your git repository. You can do this by running the following command in your terminal:

git remote add upstream https://github.com/your-organization/nativeexpress.git

If you have done this in the setup before, you can skip this step.

Update Your Repository from the NativeExpress Repository

To pull the latest changes from the NativeExpress repository, use the following command:

git pull upstream main --allow-unrelated-histories --rebase

If you encounter any merge conflicts, you'll need to resolve them manually. If you're unsure how to do this, please refer to the Git documentation (opens in a new tab).

After Updating

After successfully updating your codebase:

1. Review the changes carefully to ensure no custom code has been overwritten.
2. Update any dependencies that might have changed:

yarn install

3. Test your application thoroughly to ensure everything still works as expected.

Troubleshooting

If you encounter issues during the update process:

1. Make sure you've committed or stashed all your local changes before updating.
2. If you're having trouble with merge conflicts, consider using a visual diff tool to help resolve them.
3. If you're unsure about any part of the process, don't hesitate to reach out to the NativeExpress support team or consult with a colleague who's familiar with git operations.

Remember, updating your codebase can be a complex process, especially if you've made significant custom changes. Always backup your project before attempting an update, and if possible, test the update process in a separate branch before applying it to your main development branch.