Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Branch filters are not as granular as with azure. We can't differentiate between pull requests and pushes with the branch name. Only PRs from other remotes follow the
pull/*
branch naming scheme.The current
only
and oldignore
didn't make sense since it would've prevented any CircleCI run (which we currently see on dependabot PRs).CircleCI should still auto-cancel builds on any branch but the default branch. If we continue to see large queues for the
l10n_*
branches then we should contact support.Ideally we want:
master
andnext
So
l10n_next
would only build once a PR is open and auto-cancel on new commits. This is how azure pipelines and netlify deploys work so I don't understand why CircleCI works different.