Closed rarkins closed 1 year ago
Dashboard mockup idea:
This issue contains a list of Renovate updates and their statuses.
These branches can be created by Renovate on-demand once you click their checkbox below.
@jest/globals
, @jest/reporters
, @jest/test-result
, jest
, jest-circus
) 👶 Tick any checkbox below to manually force creation of any of the following:
@typescript-eslint/eslint-plugin
, @typescript-eslint/parser
, eslint-plugin-import
)Reference: ☑️ Needs manual approval in dashboard 📆 Awaiting scheduled branch creation time 👶 Package is awaiting stabilityDays completion 🚦 Rate limited 🚀 Automerge enabled
Maybe move the emojis after checkbox for better alignment?
Mockup showing a mix of both:
This issue contains a list of Renovate updates and their statuses.
These branches can be created by Renovate on-demand once you click their checkbox below.
@jest/globals
, @jest/reporters
, @jest/test-result
, jest
, jest-circus
) 👶 Tick any checkbox below to manually force creation of any of the following:
@typescript-eslint/eslint-plugin
, @typescript-eslint/parser
, eslint-plugin-import
)Reference: ☑️ Needs manual approval in dashboard 📆 Awaiting scheduled branch creation time 👶 Package is awaiting stabilityDays completion 🚦 Rate limited 🚀 Automerge enabled
Reasons why I'm not sure to do that:
🤔 is it possible to use checkboxes in tables? so we use tables for alignment?
It's not possible inside tables, last time I checked
🤔 is it possible to use checkboxes in tables? so we use tables for alignment?
It's not possible inside tables, last time I checked
It's still not working (at least not on GitHub).
Example table with non-functional checkbox:
Checkbox | Name | Emoji |
---|---|---|
- [ ] | ESLint | ☑️ |
Raw Markdown:
| Checkbox | Name | Emoji |
| --- | --- | --- |
| - [ ] | ESLint | ☑️ |
Maybe move the emojis after checkbox for better alignment?
I like it better when the text is properly left-aligned. Also this way we can also add a Merge Confidence "confidence" badge at the end of the text as well:
Ok, agreed. Was just an idea. 🤗
Stupid idea incoming, but would it be cleaner to removate the semantic commit prefixes, or even more text?
We can get pretty long lines as is, and those lines will only get longer if we eventually add Merge Confidence badges...
rarkin's mockup:
@jest/globals
, @jest/reporters
, @jest/test-result
, jest
, jest-circus
) 👶Remove semantic commit prefixes
@jest/globals
, @jest/reporters
, @jest/test-result
, jest
, jest-circus
) 👶Remove semantic commit prefixes + update text
@jest/globals
, @jest/reporters
, @jest/test-result
, jest
, jest-circus
) 👶"Remove semantic commit prefixes" is maybe a possibility. Maybe we can make it templated so that users can pick either.
Sounds good. I like the idea to have the text as short as possible.
@rarkins Do you want a separate issue for the "remove semantic commit prefixes" idea?
I've hidden a bunch of comments here as I want to remain focused on the branch state caching first, and dashboard reuse of it second
Blocked by #11426
A branch can be in three main states:
Reasons why a branch doesn't exist:
Reasons why a PR doesn't exist:
States which a PR can be in:
This can also be used for more accurate Dependency Dashboard