Dependency Dashboard: add reason for pending status check

[setchy]

On the Dependency Dashboard, it would be helpful to annotate dependencies in the Pending Status Checks section with the reason for the branch update being pending (ie: minimum stability days, etc)

[jamietanna]

Do we currently report that in the debug logs?

Makes sense to make something user-facing (while being cautious about platform limits)

[setchy]

Do we currently report that in the debug logs?

@jamietanna - I did have a brief look last week through the code but didn't see anything

[jamietanna]

OK, I'd be happy if you can create a couple of Issues off this:

• Add debug logs to indicate why pending status checks are in place for given branches
• Add user-facing indication to Dependency Dashboard

We'll start with debug logs, work out what the best way of presenting them (and if there are additional branch results/statuses/etc that need to be surfaced) and then we'll make them user-facing

[setchy]

Created, but auto-locked. Can you please help reopen them @jamietanna

1. Status Checks: Add debug logs for pending status check reason #40370
2. Status Checks: Add pending status check details to Dependency Dashboard #40371

[rQcAnE4pk15VDHVa]

@jamietanna - This would be so much more helpful. I just "wasted" half a day trying to better understand how Renovate works internally because I was wondering why some library updates that were older than 60 days were not being created. After reading through countless configuration parameters and throwing different tokens at it, I'm not much further. 🙂

[jamietanna]

Now there are Issues there, all it takes is someone to work on them - contributions welcome!