Source Control for other Git Providers
Don't see your Git provider in our list of Supported Git Providers? No problem. You can also use the Superblocks CLI to configure Source Control for any git provider.
caution
Note that branches are only available when using a supported Git provider. Using this guide, you'll be able to import and export changes to the main branch of your Application.
Development Workflow
The development workflow for unsupported git providers is slightly different from the flow for supported providers. The Superblocks CLI works with files stored in the file system to let you export your Applications from Superblocks, as well as import them back into Superblocks.
The CLI can also be integrated into your team's CI/CD workflow to automatically sync code changes back to Superblocks.
Exporting Changes
The superblocks pull command is used to export the latest changes made to your Superblocks Applications to your git repository. The pull command can be run as follows:
superblocks pull [PATH_TO_APP] [--mode=latest-edits|most-recent-commit]
Once your Application is exported, check diffs in your Application's files to see what was changed in your Application.
Committing to Git
With the Source Control CLI based workflow, you'll use the Git CLI to commit and push your changes to your remote repository by running:
git add [FILES]
git commit -m [MESSAGE]
git push origin/[BRANCH]
Importing Changes
When you're ready to apply new changes to Superblocks, you can use the superblocks push command to import your code:
superblocks push [PATH_TO_APP]
Once changes are imported back into Superblocks, you'll be able to Deploy your commit to make it available to end-users.
caution
Make sure that you've committed and run the pull command before running this command. It will create a new commit with your changes at the top of your Application's commit history.