This is a collection of modules and scripts that lived more than expected but aren't full blown packages. They live in this happy middle ground where they are reusable, but not polished nor fully featured.
This is simply a quick way to read ticket details from Emacs. Might skip you a trip to the browser,
but if you need to add comments or change a ticket status, then you need to jump to Firefox.
The name isn't "jira-viewer" because I might add more features. Once upon a time, this would print a list of the tickets assigned to me for a sprint, but I never bothered to update that for "other companies", I rarely used it.
The only command is
jira-show-issue, which will prompt for a ticket in the minibuffer. If the
symbol under point "looks" like an issue, it will suggest it as input.
You can bookmark a ticket using
b while reading it, or
q to quit the window.
(use-package jira-tools :load-path "/path/to/this/directory"
You need to create a token in JIRA and add it to any
auth-source enabled location, for example in
machine thecompany.atlassian.net login email@example.com password your-token-here
An older set of commands that I haven't revisited yet.
It wraps the GitHub CLI and parses some of its output. As it is now, it is more of a proof of concept.
Writing this was much easier than trying to use the GH API, which is what I guess I should have done :)
Promoted to a standalone package: https://sr.ht/~sebasmonia/confluence-reader.el/
Activate a virtual environment inside Emacs, by doing more or less the same things the
activate bash script does. It also modifies
exec-path so running a Python
inferior process goes to the right version of the interpreter.
I could probably use https://github.com/jorgenschaefer/pyvenv, but it is more oriented to
virtualenvwrapper and some other tools that I probably won't use. I did look at its code for
guidance. This package is much smaller, and also more limited. For example, no auto-switching of
venvs, and before activating a second one, you need to deactivate the one currently active.
It works for me because I usually work in each project (and venv) for a long stretches :)
(use-package pyvenv :load-path ""/path/to/this/directory""