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've linked this issue in the todo list of #7247 but please don't extract other items to dedicated issues. PER-CS support doesn't need to be provided at once (rather PR per todo list item), but also atomic PRs don't need atomic issues, and can be referenced to the main one. Some todo items have issues/PRs linked because these were already created. Creating new ones will only cause more maintenance burden (stale bot) and will increase the size of the backlog.
Since this issue has not had any activity within the last 90 days, I have marked it as stale.
The purpose of this action is to enforce backlog review once in a while. This is mostly for maintainers and helps with keeping repository in good condition, because stale issues and PRs can accumulate over time and make it harder for others to find relevant information. It is also possible that some changes has been made to the repo already, and issue or PR became outdated, but wasn't closed for some reason. This action helps with periodic review and closing of such stale items in automated way.
You may let maintainers handle this or verify current relevancy by yourself, to help with re-triage. Any activity will remove stale label so it won't be automatically closed at this point.
I will close it if no further activity occurs within the next 30 days.
Feature request
extracted from #7247
expected output:
helpful also for coverage measurements
The text was updated successfully, but these errors were encountered: