denoland / denoland/deploy_feedback

[Bug]: Don't deploy on every push

Open
#634 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
No language data
Stars
79
Forks
5
PR merge metrics
No merged PRs in 30d

Description

### 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! :)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.