Replies: 2 comments
-
|
Ahhh I've come back after a night's rest and thought more about - #676 - which I had found last night. I then cobbled together: (defun forge-list-global-pullreqs-authored ()
(interactive)
(when-let (((forge-db t))
(repo (forge-get-repository :tracked?))
(user (ghub--username repo))
(spec (clone forge-status-buffer-default-topic-filters)))
(oset spec author user)
(forge-topics-setup-buffer nil spec :type 'pullreq :global t)
(transient-setup 'forge-topics-menu)))This seems to work pretty well. Though it will only work for the |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I've just added examples to the docstrings of |
Beta Was this translation helpful? Give feedback.
0 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.
-
Foreword
First off I want to thank you for the wonderful
forgeandmagitpackages I've been a grateful user for many years and don't know where
I would be without them.
The new topic view is additionally really nice and the new filtering
functions seem much more intuitive. This seems like a step right
direction in a big way.
Background
Before the recent refactor it was easy for me to define a function to
list all pull-requests that were owned by me. I would use this to
check on my pull-requests and see if there were any that I needed to
address issues with, bump, or generally continue working on. The code
was probably not very elegant but roughly looked like:
I essentially looked through all of my
forge-owned-accountsandcreated a new pullreq view from that list.
Problem
Generally it is no longer terribly clear how I can easily pass an
author to
forge-list-global-pullreqssuch that I can redefineforge-list-authored-pullreqsin this new world.This is further exacerbated by an issue where, when looking at the
global topicslist I am able to filter by the author but thepre-generated list of authors is subtly misleading. It is generated by:
This list of authors is actually the list of assignees from the
current repository instead of some global list or a list that is
made to include the owned repositories like:
Solution
I think a way to pass in an author or more "filter" information to
forge-list-global-pullreqswould make it much more flexible forothers to look at this view as they want.
It would be great if one or more of:
forge--read-filter-by-userwas made to behave differently in aglobal view
forge--read-filter-by-userwas made to always include the ownedaccounts
forge--read-filter-by-authorwas made to behavedifferently from the user variant
I'm not sure how much of this is considered a "bug" vs. a "feature"
but I figured I should go via discussions. I hope this is the right spot.
Beta Was this translation helpful? Give feedback.
All reactions