Publish the API with GitHub Actions

You added your API to your web app and they’re both running locally. Now it’s time to publish your API and your app to Azure Static Web Apps.

When you created the Azure Static Web Apps instance and asked it to watch your main branch, a GitHub Action was generated for you. The GitHub Action listens to your repository’s main branch for commits and pull requests. Then when the GitHub Action detects these changes, it builds and publishes your app.

When you created your Azure Static Web Apps resource, you provided the folder location for your API project by accepting the default value of Api. Azure Static Web Apps built and deployed the Azure Functions app in that folder. However, the app didn’t work because the HTTP GET API isn’t created yet.

Trigger the GitHub Action

The GitHub Action is ready to build and publish your web app and API once it detects a change to your main branch. You could either commit directly or create a pull request to the main branch. Both of these changes trigger the GitHub Action. When changes are detected on the main branch, it triggers the GitHub Action to publish the app at the same URL for your live web site.

sap erp procurement material management training courses malaysia