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
First, I love this work. I am using it now and thinking of ways to use it more. Thank you!
I find myself watching the interactive updates (they are so cute) during the rev dep checks. Last time I was watching the progress, I had a thought about a potential improvement to the format the information is displayed. Many reverse dependencies are packages totally out of our control and I am not really concerned whether or not there is an error/warning/note in the checks on any single version. Rather, I want to see whether there are new error/warning/notes using the dev version for the check. Perhaps a counter that had one row per rev dep and reported on new error/warning/notes would be more informative?
The text was updated successfully, but these errors were encountered:
This would be amazing, and I think it should be pretty manageable. Maybe we could do something like this:
│ S │ OK N W E │
─ gtsummary ──────────────────┼───┼─────────────┼──────────────────────────────────────────
+cards (v0.2.2) │ ✓ │ 47 0 0 0 │ 2.5s
+cards (dev v0.2.2.9000) │ W │ -2 +1 +1 0 │ 2.5s
─ cardx ──────────────────────┼───┼─────────────┼──────────────────────────────────────────
+cards (v0.2.2) │ ✓ │ 40 0 0 0 │ 2.5s
+cards (dev v0.2.2.9000) │ ◓ │ 22 0 1 0 │ 3.6s checking if there is a namespace ...
When in progress, the task is reporting the total of each category, and once it finishes it reports the diff. I like this style because it groups the information, but it's still a bit hard to scan visually to see which packages are problematic. We could maybe find a way to highlight each group with an indicator after both the release and dev jobs have finished.
First, I love this work. I am using it now and thinking of ways to use it more. Thank you!
I find myself watching the interactive updates (they are so cute) during the rev dep checks. Last time I was watching the progress, I had a thought about a potential improvement to the format the information is displayed. Many reverse dependencies are packages totally out of our control and I am not really concerned whether or not there is an error/warning/note in the checks on any single version. Rather, I want to see whether there are new error/warning/notes using the dev version for the check. Perhaps a counter that had one row per rev dep and reported on new error/warning/notes would be more informative?
The text was updated successfully, but these errors were encountered: