-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
netlify: force rebuild with every merge to avoid 'failed' message in badge #1640
Conversation
a5383e8
to
c89b512
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, they say the request to fix this was submitted a year ago and still nothing! As far as we don't trigger tons of empty deployments, this solution should work fine 👍🏼
@@ -2,6 +2,7 @@ | |||
base = "src/frontend/next/" | |||
publish = "out" | |||
command = "npm run build" | |||
ignore = "/bin/false" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's add a comment above this line linking to this PR, which documents why we do this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
af634f2
c89b512
to
af634f2
Compare
af634f2
to
7621974
Compare
Description
Whenever a PR is merged and no changes were made to
next
, our badge reports afailed
build. This happens becausenetlify
detects that no changes were made to thenext
front-end and cancels the build, and for some reason it considers this a failed attempt.This bug has been reported, and it seems that the solution to avoid this behavior (for now) is to force a build even when no changes were made to the
next
front-end.This PR makes the necessary changes to our
netlify.toml
to force thenext
build.