Next: Creating Topics, Previous: Visiting Topics, Up: Working with Topics [Contents][Index]
By default Forge lists a subset of topics directly in the Magit status buffer. It also provides commands to list topics and notifications in separate buffers.
Forge adds the following two functions to magit-status-sections-hook:
This function inserts a list of the most recent and/or open pull-requests.
This function inserts a list of the most recent and/or open issues.
This option limits the number of topics listed by the above functions.
All unread topics are always shown. If the value of this option has
the form (OPEN . CLOSED), then the integer OPEN specifies the
maximal number of topics and CLOSED specifies the maximal number of
closed topics. IF CLOSED is negative then show no closed topics
until the command forge-toggle-closed-visibility changes the sign.
This command toggles whether the above two functions list recently closed issues in the current buffer.
The following three functions are also suitable for
magit-status-sections-hook:
This function inserts a list of open pull-requests that are assigned to you.
This function inserts a list of open pull-requests that are awaiting your review.
This function inserts a list of open pull-requests that are authored by you.
This function inserts a list of open issues that are assigned to you.
This function inserts a list of open issues that are authored by you.
The following commands list repositories, notifications and topics in dedicated buffers:
forge-list-repositories)This command lists all known repositories in a separate buffer.
forge-list-notifications)This command lists all notifications for all forges in a separate buffer.
forge-list-pullreqs)This command lists the current repository’s pull-requests in a separate buffer.
forge-list-issues)This command lists the current repository’s issues in a separate buffer.
This command lists the current repository’s open pull-requests that are labeled with a label read from the user.
This command lists the current repository’s open issues that are labeled with a label read from the user.
This command lists the current repository’s open pull-requests that are assigned to you in a separate buffer.
This command lists the current repository’s open issues that are assigned to you in a separate buffer.
This command lists pull-requests of the current repository that are awaiting your review in a separate buffer.
This command lists the current repository’s open pull-requests that are authored by you in a separate buffer.
This command lists the current repository’s open issues that are authored by you in a separate buffer.
This command lists open pull-requests from all the repositories that
you own. Options forge-owned-accounts and forge-owned-ignored
controls which repositories are considered to be owned by you. Only
Github is supported for now.
This command lists open issues from all the repositories that
you own. Options forge-owned-accounts and forge-owned-ignored
controls which repositories are considered to be owned by you. Only
Github is supported for now.
This is an alist of accounts that are owned by you. This should
include your username as well as any organization that you own.
Used by the commands forge-list-owned-issues,
forge-list-owned-pullreqs and forge-fork.
Each element has the form (ACCOUNT . PLIST). The following
properties are currently being used:
remote-name The default name suggested by forge-fork for a fork
created within this account. If unspecified, then the name of the
account is used.
Example: (("tarsius") ("emacsmirror" :remote-name "mirror")).
This is a list of repository names that are considered to not be
owned by you even though they would have been considered to be owned
by you based on forge-owned-accounts.
Next: Creating Topics, Previous: Visiting Topics, Up: Working with Topics [Contents][Index]