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 using this app we're getting lots of pull requests in the done column of the board. This is not really expected because it doesn't look like CI ever failed for those pull requests.
I wonder if PRs are being added to the board in circumstances other than CI failing for them.
The text was updated successfully, but these errors were encountered:
I analysed all the Pull Requests created by dependabot currently in the bench board and every one of them had a failing workflow at some point, therefore I conclude that the issue is not related to unbreakci. Around 10% of these PR were actual issues with Build or Test commands. The significant others were grouped in three major categories:
Pull Request is not mergeable: Where the action tried to merge before the approved status of the PR, probably related to GitHub. No action was taken.
GitHub sync: Where workflow didn't wait for a prior job used in needs field, also probably related to GitHub synchronisation. No action was taken.
PR is not from Dependabot, nothing to do: Missing filter on push to master/main branch was triggering the workflow incorrectly and actions used in this composite were failing. Workflows within this category were updated in the repositories present in the spreadsheet. I'll keep an eye for future ones. A Pull Request was submitted to update the readme of the action with correct filters.
When using this app we're getting lots of pull requests in the done column of the board. This is not really expected because it doesn't look like CI ever failed for those pull requests.
I wonder if PRs are being added to the board in circumstances other than CI failing for them.
The text was updated successfully, but these errors were encountered: