You can stay updated about the latest commits to Fire App Builder by watching and starring the project in Github. You can also periodically check the Release Notes page in the documentation.
When new versions of Fire App Builder are released and pushed out to Github, you can get the new version’s updates and integrate the code into your project using the common
git pull technique used with Github workflows.
First change to your fire-app-builder directory (or whatever you’ve named it). Then pull the latest changes into your repository:
cd fire-app-builder git pull
When you run a
git pull command, git downloads the latest updates from the original repository and attempts to merge the updates into your code.
Resolving Merge Conflicts
If changes in the original repository’s files conflict with changes you’ve made to your local copy, git will not automatically overwrite your local copies with the updates. Instead, git will show you merge conflicts for the affected files and remove the affected files from its tracking. You will then need to resolve the merge conflicts, add the files back into git tracking, and commit your update.
After you run
git pull, if you see merge conflicts, pen the files with merge conflicts. Carrots (»»») and («««) indicate areas where conflicts occur. Manually edit the files to remove the carrots. Then add the file back into git tracking with
git add <filename>, where
See Resolving a merge conflict from the command line for details on how to resolve merge conflicts.
Here are some good resources for learning git: