Not necessarily a bug, but since I have the frontend and backend parts of my WebApp in one repo, every time I push something in the frontend, deno deploy starts a new build and deploys it, although nothing has changed.
Is there a possibility to prohibit deno from building? The main entrypoint is set to my server.ts in the backend folder, but still it builds every time (even on README changes)
Steps to reproduce
Happens on every push
Expected behavior
Only build and deploy, when file inside the backend folder are altered
Problem description
Not necessarily a bug, but since I have the frontend and backend parts of my WebApp in one repo, every time I push something in the frontend, deno deploy starts a new build and deploys it, although nothing has changed.
Is there a possibility to prohibit deno from building? The main entrypoint is set to my server.ts in the backend folder, but still it builds every time (even on README changes)
Steps to reproduce
Happens on every push
Expected behavior
Only build and deploy, when file inside the backend folder are altered
Environment
No response
Possible solution
No response
Additional context
Your help is much appreciated! :)