Once I'm actually up and running and the app is public, I obviously won't want to be hitting the deploy button in gadget from development, as I'll then be actually creating individual branches for features/bugs/hotfixes etc, how should I go about then getting that feature branch into production?
Should I stop using the deploy button in Gadget and setup a github workflow for push into production/main to do a build then push gadget files? So when merging a feature/bug/hotfix branch into my production/main branch, it will trigger the workflow.
I'm just reading these docs and it uses the following:
name: CI/CD Pipelineon: push: branches: - main # or any other branch you want to deploy fromjobs: deploy: steps: - name: Checkout the current repository uses: actions/checkout@v4 - name: Deploy to Gadget Production uses: gadget-inc/ggt-deploy-action@v1 with: app: '<your-app-name>' environment: '<your-environment>' # The environment you are deploying to production token: ${{ secrets.GGT_TOKEN }} # Add your CLI token allow-issues: 'false' # Optionally, continue deployment even if there are issues
name: CI/CD Pipelineon: push: branches: - main # or any other branch you want to deploy fromjobs: deploy: steps: - name: Checkout the current repository uses: actions/checkout@v4 - name: Deploy to Gadget Production uses: gadget-inc/ggt-deploy-action@v1 with: app: '<your-app-name>' environment: '<your-environment>' # The environment you are deploying to production token: ${{ secrets.GGT_TOKEN }} # Add your CLI token allow-issues: 'false' # Optionally, continue deployment even if there are issues
What actually defines this as a 'deploy to production' action? Does this perform a build too? I'm guessing its based off the