You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] Function App will not work when deployed using Github Actions. #1722
I have been trying for days to get this to work.
I can deploy my function app from the VS Code extension and it works fine.
I am deploying using Github Actions, the exact script that is generated for me by Azure.
All my tests are passing in my Github Actions pipeline.
There are no errors in the pipeline.
It says deployment was successful. After deployment my function cannot be found.
It is SO frustrating to me that I can easily deploy using a click from VS Code, but the EXACT SAME CODE, pushed in the exact way that Azure recommends, does not work.
Please note that, when deploying through the VS Code extension, remote build is used. For GitHub actions, depending on the plan, either one deploy or zip deploy is used.
The main difference in these technologies is that in your GitHub pipeline, you'll need to directly install the dependencies into the .python_packages folder like so: pip install -r requirements.txt --target=".python_packages/lib/site-packages"
An example step for installing the dependencies looks like this:
hallvictoria Thank you for your help. When I was trying to set up my function app, I could not find those links that you posted. They would have been helpful.
Here is my question: when I connect my function app to my Github account in the deployment center, Azure creates a deployment workflow yaml. That yaml does not look anything like the example you showed me. Is the yaml that Azure generates during that step wrong? If so, why would Azure go to all the trouble of connecting Github and Function Apps, and then not bother to generate a correct, working yaml file?
It would be REALLY nice if I could just connect the github repo and the function app during setup and never have to touch the YAML again.
Activity
hallvictoria commentedon Jul 22, 2025
Hi Tyler (@Tylersuard), thanks for reporting.
Are you following the Continuous delivery for Azure Function Apps using GitHub Actions tutorial?
Please note that, when deploying through the VS Code extension, remote build is used. For GitHub actions, depending on the plan, either one deploy or zip deploy is used.
The main difference in these technologies is that in your GitHub pipeline, you'll need to directly install the dependencies into the
.python_packagesfolder like so:pip install -r requirements.txt --target=".python_packages/lib/site-packages"An example step for installing the dependencies looks like this:
The full template can be found here: Python GitHub Actions Deployment Sample
Could you provide the full pipeline script and documentation you're using?
Tylersuard commentedon Jul 22, 2025
hallvictoria Thank you for your help. When I was trying to set up my function app, I could not find those links that you posted. They would have been helpful.
Here is my question: when I connect my function app to my Github account in the deployment center, Azure creates a deployment workflow yaml. That yaml does not look anything like the example you showed me. Is the yaml that Azure generates during that step wrong? If so, why would Azure go to all the trouble of connecting Github and Function Apps, and then not bother to generate a correct, working yaml file?
It would be REALLY nice if I could just connect the github repo and the function app during setup and never have to touch the YAML again.