Replies: 1 comment 3 replies
-
|
@rovo89 Thanks for bringing this to our attention. I'll take a look at all three PRs and also change our notifications so that new PRs are treated the same as issues and notify us |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
I'm glad to see that the WDK is taking off, I love using it, I'm looking forward to future improvements, but there's one thing that I'm concerned about:
I've opened 3 PRs - 12 days (#1002), 11 days (#1023) and 2 days (#1159) ago. Nothing controversial, just two small (but important) bugfixes and a performance config that we discussed about before. So I don't expect many discussions and little review effort.
Until now, there has been zero reaction on any of these, not even enabling the workflows. That's not only a bit demotivating, these are also changes that have a significant impact on our app. Running a fork is far from trivial due to the amount of packages and the mono-repo setup.
My fear is that the list of open, uncommented PRs and issues will grow exponentially as usage increases. I'm sure you have a very full backlog, and I'm not a fan of personally pinging people.
So... do you maybe have an agent which could take care of prequalifying PRs and issues, flagging human staff when it can't answer? For PRs, it could estimate review effort and how well it fits to the project goals, giving a list of quick wins, big features or critical bugs that can be worked when time allows. I've seen some of this in other repos - maybe Vercel has something for this?
Beta Was this translation helpful? Give feedback.
All reactions