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
Hi! I'm just starting to get comfortable with forge, so probably finding some rough edges that might be a non-issue for daily users. I opted to check out only some topics, so all solutions involving "just fetch everything" are not suitable.
When visiting a topic, I expected there to be an easy way to fetch it for getting new posts. C-c C-c / f is available and of course N f t RET (since the latter asks for the topic number again). Shouldn't this be easier by default, e.g. C-c C-f to "fetch the thing"? The most convenient way should be mentioned in the docs section 6 "Visiting Topics" IMHO.
Next best choice would be a quick way to refresh all topics already in the current list (within magit status or the separate topics list buffer). I expected f n to do that, but apparently the new posts did not end up in the buffer visiting a specific PR. As if nothing was actually pulled - it's not quite clear what should be (all topics? refresh existing? current thing?) Even better if the active region would be respected, to fetch only marked topics (ref. Act on multiple issues at once #305).
It seems cumbersome to keep only certain topics locally. Is there a way to pull only open issues/PRs? #693 asked for limiting to open topics initially, but after some months you will (hopefully) end up with local entries for closed ones anyway. Cleaning that out should be easier than M-x forge-remove-topic-locally, as that operates only on a single entry. Marking several lines would be great here, and maybe a default binding for the k key, like other contexts in magit status. Combined with filtering, forgetting about closed stuff locally would be rather quick. And the hint for the + binding in Delete topic LOCALLY only (+ for all): doesn't seem to work for me. I can only enter a number, but when hitting + it simply does nothing. That would have been plan B, delete everything locally and fetch specific ones again.
Somehwat unrelated, I'm getting the hang of how forge and branch pulling interact. But I thought I had seen the related branch or head commit of a PR listed when expanding (TAB) the respective line in a PR list. But that no longer works, it just hides the small arrow indicating an expandable section, without adding further detail. Is that a bug?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi! I'm just starting to get comfortable with
forge, so probably finding some rough edges that might be a non-issue for daily users. I opted to check out only some topics, so all solutions involving "just fetch everything" are not suitable.When visiting a topic, I expected there to be an easy way to fetch it for getting new posts.
C-c C-c / fis available and of courseN f t RET(since the latter asks for the topic number again). Shouldn't this be easier by default, e.g.C-c C-fto "fetch the thing"? The most convenient way should be mentioned in the docs section 6 "Visiting Topics" IMHO.Next best choice would be a quick way to refresh all topics already in the current list (within magit status or the separate topics list buffer). I expected
f nto do that, but apparently the new posts did not end up in the buffer visiting a specific PR. As if nothing was actually pulled - it's not quite clear what should be (all topics? refresh existing? current thing?) Even better if the active region would be respected, to fetch only marked topics (ref. Act on multiple issues at once #305).It seems cumbersome to keep only certain topics locally. Is there a way to pull only open issues/PRs? #693 asked for limiting to open topics initially, but after some months you will (hopefully) end up with local entries for closed ones anyway. Cleaning that out should be easier than
M-x forge-remove-topic-locally, as that operates only on a single entry. Marking several lines would be great here, and maybe a default binding for thekkey, like other contexts in magit status. Combined with filtering, forgetting about closed stuff locally would be rather quick. And the hint for the+binding inDelete topic LOCALLY only (+ for all):doesn't seem to work for me. I can only enter a number, but when hitting + it simply does nothing. That would have been plan B, delete everything locally and fetch specific ones again.Somehwat unrelated, I'm getting the hang of how
forgeand branch pulling interact. But I thought I had seen the related branch or head commit of a PR listed when expanding (TAB) the respective line in a PR list. But that no longer works, it just hides the small arrow indicating an expandable section, without adding further detail. Is that a bug?Versions: Magit 4.2.0, Transient 0.8.2, Forge 0.4.6, Git 2.43.0, Emacs 29.3, gnu/linux
Beta Was this translation helpful? Give feedback.
All reactions