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
When you use this repo as a template, all dependabot PRs that are opened will fail as they do not regenerate the dist folder.
Is there a way to make dependabot do that or to not have the weird requirement to commit compiled code?
Because currently dependabot creates a lot of churn because all the PRs it opens will fail
The text was updated successfully, but these errors were encountered:
arianvp
changed the title
Check Transpiled JavaScript action fails for Dependabot PRs
Check Transpiled JavaScript workflow fails for Dependabot PRs
Dec 23, 2024
Yeah it can be a nuisance with dependency updates, since the dist/ directory can be modified when non-development dependencies are updated. I tested this out a few different ways, and it is possible to set up a GitHub Action that ensures the dist/ directory is rebuilt on Dependabot PRs, however I opted not to include this in the template because its way too easy to end up with infinite loops when GitHub Actions runs and updates the PR branch.
I'm waiting on Immutable Actions to go GA before trying another approach. In the meantime, you may want to checkout the container action template instead. This one is pretty straightforward to set up so the container pulls the dependencies and builds as part of your CI pipeline.
Closely related to #957 but different.
When you use this repo as a template, all dependabot PRs that are opened will fail as they do not regenerate the
dist
folder.Is there a way to make dependabot do that or to not have the weird requirement to commit compiled code?
Because currently dependabot creates a lot of churn because all the PRs it opens will fail
The text was updated successfully, but these errors were encountered: