Does this help? We hope you'll accept our pull request. ;-)
And yes! We have engineering, product, and design leads supporting the PR experience who are super interested in getting your collective feedback about where we should take the experience next.
Today, we are announcing the general availability of the new and improved Projects powered by GitHub Issues. GitHub Projects connects your planning directly to the work your teams are doing in GitHub and flexibly adapts to whatever your team needs at any point.
We'd love for you to give it a try and share your feedback!
On the "Use # to search" it's not clear how that searching is supposed to work.
I tried # and then a word from the title of the issue - that doesn't seem to do anything. I
I then realized the # is supposed to be followed by the repo name, which is a bit of an extra step. However, when I'm in the repo itself already, and in the board view, then it's an unnecessary step to add the repo name again, it should probably just start searching issues within the repo right away.
I suppose what I'm getting at is, the extra step to add the repo feels like a speedbump, and not intuitive to get right away (I was expecting to just start typing and Github figures out all my issues to suggest). Maybe it's going to take getting used to.
As a result, we went back to the drawing board and rewrote the changelog from scratch to try and increase clarity: https://github.blog/changelog/2022-08-04-commit-comments-no-...
Does this help? We hope you'll accept our pull request. ;-)
And yes! We have engineering, product, and design leads supporting the PR experience who are super interested in getting your collective feedback about where we should take the experience next.