NonGNU ELPA - fj

To get going, first set fj-host, and fj-user.

To authorize your account, call fj-create-token, which will prompt you for your password, create an API access token, and copy it to your kill ring. Alternatively you can obtain an access token from your profile settings on your Forgejo instance (in user settings, under "applications").

Once you have your token, call fj-token (or any interactive function such as fj-list-issues). You will be prompted for your access token, and when you enter it, fj.el will also offer to save it in your auth-sources file (~/.authinfo.gpg or similar; see variable auth-sources). Once saved, you should be good to go.

Alternatively, you can set fj-token-use-auth-source to nil and simply set fj-token to your token (unencrypted option).

Finally, if you were previously using the unencrypted fj-token method and want to use auth sources, simply remove the code that sets fj-token in your init config, and follow the steps above.

If you run into any auth issues, feel free to open an issue or contact me.

Once you are authenticated, try fj-list-own-repos to view your repos, or fj-list-issues to view issues of the current repo, or with completing-read of a repo is no repo is found.

If you are already viewing a repo and want to force the prompt to choose another, call fj-list-issues with a prefix arg (C-u).

You can also call fj-list-own-issues to view all issues across your repos, and fj-watched-repos to see your watched repos.

To use a different instance for a given repo, set fj-host, fj-user, and fj-token in your .dir-locals.el file.

• create new (remote) repo
• delete a repo

• search and list instance repos
• list a user's repos
• fork a repo
• star a repo
• watch a repo
• copy clone URL of repo
• view a repo's readme
• view a repo's commit log
• list repo's stargazers
• list repo's watchers

• list repo issues and PRs
• list issues in any repo you own
• list issues you have authored in any repo
• cycle between issues/PRs/all
• cycle between open/closed/all issues/PRs
• sort issues/PRs (serverside)
• quick jump to any issue/PR or repo in a listing with imenu.
• search in repo issues/PRs

• act on an issue/PR from the listing (edit, edit title, comment, close, reopen, delete, add label)

• view issue/PR discussion
• act on issue/PR (as above, plus reply or delete comment)
• jump to mentioned user, issue or commit.
• display all issue/PR timeline items (references, commits, merges, close/reopen, edit, etc.)
• display diff of any commit
• display diff of entire PR
• PR review discussion
• PR review diffs
• merge PR
• browse URL of view or entry at point
• add reactions to item at point
• add labels to item.

• view your notifications
• jump to relevant item
• toggle between viewing unread and all notifications

• update repo settings transient menu
• update user settings transient menu

• view followers
• view users followed

Unfortunately fj.el is pretty slow at loading issues/PRs with lots of comments and other timeline elements. The relevant code was recently re-written to be partly async, and the rendering of HTML in item bodies was recently overhauled, but the performance is still terrible. This leads me to believe it is actually to do with the Forgejo API (as for example, my abominable old rendering code worked for 100+ items with Lemmy, but couldn't do 30 items in a timely manner with Forgejo.)

There is a defcustom, fj-timeline-default-items, with a default value of 15, meaning we load 15 timeline elements by default. If you find the performance is no problem on longer items, you can increase this value. (The default apart from this setting would be 30.)

fj.el started out as a tiny package around my general use-case: working with repos I own and that have few if any collaborators and only one remote. Working with other repos was added later, and some workflows and commands still need adjusting in this regard. If you find fj.el generates a lot of friction with your workflow, feel free to let me know. (It's not easy hacking in the vague direction what I imagine other people's workflows to be.)