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
I'm just brainstorming about the ways that will help us noticing, assigning, and addressing failing remote tests in a timely manner. One way would be a dashboard, or another a github action that also pings those who are maintaining the given module: #1446 (if there is someone at archives, the rest of the modules would remain in the "best effort" category by the library maintainers).
E.g. the list in #2203 will become outdated very soon.
The text was updated successfully, but these errors were encountered:
A dashboard sounds useful; can we use the gh projects pages for this? or is there some other automated tool? I don't think it's a good use of limited for us to build a dashboard when there are so many dispersed failures.
I think the gh pages would require issues to be created for each items (otherwise people would not be assigned anyway). I think that would be a bit of a noise-generating for the main repo, which may still be OK. Or technically those isses could go into a separate repo.
Anyway, if someone feels the urge of playing with a bit of github API, build a custom actions and make this work, it would be a great addition of infrastructure :)
I'm just brainstorming about the ways that will help us noticing, assigning, and addressing failing remote tests in a timely manner. One way would be a dashboard, or another a github action that also pings those who are maintaining the given module: #1446 (if there is someone at archives, the rest of the modules would remain in the "best effort" category by the library maintainers).
E.g. the list in #2203 will become outdated very soon.
The text was updated successfully, but these errors were encountered: