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
It's more for the user to be able to prioritize which issue they want to investigate. From my own experience, when I first looked at the issues list, I found some issues that were interesting and clicked in to look at the descriptions and thought about potential causes/fixes. But while looking through the github history I realised that someone had already pushed a fix tagged to those issues. Ideally, I would be made aware of this right at the request list page and I could have spent that time/effort looking at other unsolved issues.
In the future we plan to add staking if you start working on the issue, so should other users that you have picked up the request. Would that satisfy your need?
Having the information that you describe on the overview page would mean that we have to query the api of github for each issue, that would degrade performance.
Expected behaviour
Each request on this page should show a count of relevant PRs and commits
https://fundrequest.io/requests
Actual behaviour
This information is not available
Steps to reproduce the behaviour
The text was updated successfully, but these errors were encountered: