@Ian De Leon Just checking if you are still facing issue here,
When using GitHub Actions, the code is deployed to your function app using Zip deployment for Azure Functions.
Could you confirm if sets a subpath in your repository from which to publish. By default, this value is set to .
, which means all files and folders in the GitHub repository are deployed.
see- parameters are most commonly used.
If you are using VS Code for development, consider utilizing the VS Code Azure Tool Extension. The extension is designed to enhance Azure-related functionalities within VS Code, which might help you tackle the problem more effectively.
Also, In the context of the Azure App Service, navigate to the "Deployment Center" blade. This refers to a specific section or feature within the Azure portal related to managing deployments. Once you are in the "Deployment Center" blade, look for a button labeled "Disconnect" at the top.
Clicking on this button will disconnect any existing connections or configurations associated with your app's deployment. After performing this disconnection, proceed to re-run the release pipeline. This will initiate the deployment process again, and it may potentially fix the issue you encountered during the previous deployment attempt.
Also see if issue is due to authentication, GitHub Actions to authenticate with Azure Functions for deployment is by using a publish profile. You can also authenticate using a service principal. To learn more, see this GitHub Actions repository.
Hope this helps.