Moving between completing-read and the topic list

[glasserc]

Now I understand how the topics list works but I feel like it could interoperate a little nicer when operating on commands using completing-read.

To recap, at work there's a big Github repository that essentially everyone works on, and it tends to have about 1000 open PRs plus tens of thousands of PRs in its history. The operation I tend to use the most in forge is to check out a branch from a PR, which I used to initiate by doing b f, but I think b f is limited to the newest 200 / newest active 200 PRs. Instead I will be using the topic list to filter the set of PRs and then put point on the one I want, and then do b f RET there.

• I wish there was a way to go from the minibuffer/completing-read of b f to the topic list. My muscle memory is to start with b f from the Magit status buffer, and it feels a little unfortunate that I have to "back out" (C-g and then N l t go to the topic list) if the topic I want doesn't happen to be in the newest 200. Alternately, maybe it would be nice to have a way to use the topic filtering commands when in the minibuffer, but I infer that the direction the project is going is to make more use of topic lists, so maybe that's not as good an idea.

• I wish there was a way to use the currently-filtered list of topics as the set for a completing-read. So, I could use the topics buffer to filter down to the PRs from a specific person, and then use something like b f to choose from only this set. As it is, it lets me select from the normal "newest 200 + whatever point is on", which seems less useful to me. This is true for all the commands in the "dispatch" menu too, which I found a little surprising.

[tarsius]

To be able to focus on other projects, I have to reduce the time I spend on Forge. That involves deciding to not implement certain features and I'm afraid this is one of those. Sorry.