Plugin to work with GitHub issues and PRs from Neovim. Just edit the issue description/comments and save it with :w. Modified description or comments are highlighted in the signcolumn.

Use your favourite plugin manager to install it. eg:

Plug 'pwntester/octo.nvim'

• Install GitHub CLI
• Install telescope.nvim

Plug 'nvim-lua/popup.nvim'
Plug 'nvim-lua/plenary.nvim'
Plug 'nvim-telescope/telescope.nvim'

-- To use Telescope interface for octo pickers 
lua require('telescope').load_extension('octo')

There is only an Octo <object> <action> [arguments] command:

• If repo is not provided, it will be derived from <cwd>/.git/config.

If no command is passed, the argument to Octo is treated as a URL from where an issue or pr repo and number are extracted

Examples:

Octo https://github.com/pwntester/octo.nvim/issues/12
Octo issue create
Octo issue create pwntester/octo.nvim
Octo comment add
Octo reaction add hooray
Octo issue edit pwntester/octo.nvim 1
Octo issue edit 1
Octo issue list createdBy=pwntester
Octo issue list neovim/neovim labels=bug,help\ wanted states=OPEN

Just edit the issue title, description or comments as a regular buffer and use :w(rite) to sync the issue with GitHub.

• Open the PR (eg: Octo pr list or Octo pr edit XXX)
• Start a review with Octo review start or resume a pending review with Octo review resume
• Quickfix will be populated with the changed files
• Change quickfix entries with ]q and [q or by selecting an entry in the quickfix window
• Add comments with <space>ca or :OctoAddReviewComment on single or multiple lines
• Add suggestions with <space>sa or :OctoAddReviewSuggestion on single or multiple lines
• Edit comments/suggestions with <space>ce
• A new split will open. Enter the comment and save it (:w). Optionally close the split

• Add as many comments as needed
• Review comments with Octo review comments
  • Use to jump to the selected comment
  • Use to edit the selected comment
  • Use to delete the selected comment

• When ready submit the review with Octo review submit
• A new float window will pop up. Enter the top level review comment and exit to normal mode. Then press <C-m> to submit a comment, <C-a> to approve it or <C-r> to request changes

• Open the PR (eg: Octo pr list or Octo pr edit XXX)
• Open review threads view with Octo review threads
• Quickfix will be populated with the changed files
• Change quickfix entries with ]q and [q or by selecting an entry in the quickfix window
• Jump between comments with ]c and [c
• You can reply to a comment, delete them, add/remove reactions, etc. as if you where in an Octo issue buffer

• Issue/PR id completion (#)
• User completion (@)

<Plug>(OctoOpenIssueAtCursor): Open issue/pr at cursor with Octo

The term GitHub color refers to the colors used in the WebUI. The (addition) viewer means the user of the plugin or more precisely the user authenticated via the gh CLI tool used to retrieve the data from GitHub.

• g:octo_date_format: Date format (default: "%Y %b %d %I:%M %p %Z")
• g:octo_remote_order: Order to resolve the remote for the current working directory (default: ["upstream", "origin"])
• g:octo_qf_height: Percent (when 0 < value < 1) or absolute (when value > 1) height of quickfix window (defaults to 20% relative)
• g:octo_bubble_delimiter_left: Left (unicode) character to draw a bubble for labels etc. (default: "")
• g:octo_bubble_delimiter_right: Right (unicode) character to draw a bubble for labels etc. (default: "")
• g:octo_icon_user: Icon used to signal user names (default: "")
• g:octo_icon_reaction_viewer_hint: Icon as alternative or to complement the highlighting of reactions by the viewer himself (default: "")
• g:octo_snippet_context_lines: Number of additional lines displayed from the diff-hunk for single-line comments (default: 3)

How can I disable bubbles for XYZ?

Each text-object that makes use of a bubble (except labels) do use their own highlight group that linkes per default to the main bubble highlight group. To disable most bubbles at once you can simply link OctoNvimBubble to Normal. To only disable them for a certain plain do the same for the specific sub-group (e.g. OctoNvimUser).

Why do my issue titles or markdown syntax do not get highlighted properly?

The title, body and comments of an issue or PR are special as they get special highlighting applied and is an editable section. Due to the latter property it gets the OctoNvimEditable highlighting via a special signs linehl setting. This takes precedence over the buffer internal highlights. To only get the background highlighted by the editable section, set OctoNvimEditable to a highlight with a background color definition only.