GitHub integration
Review and check out pull requests, submit reviews, open a file on GitHub at the caret line, and jump from a failed CI log straight to the offending line. Uses your own gh CLI, so Editora never handles a token.
GitHub, through the gh CLI you already have signed in. Editora never handles a token: it shells out to gh the same way the Git support shells out to git, so GitHub Enterprise works with no extra setup.
- Review a pull request in the editor. A Files changed tab lists every file with its status and per-file
+/−counts; click one for a read-only diff. The description renders as Markdown above the list, andn/pstep through changes. - Submit a review, approve, request changes, or comment, without leaving the editor.
- Check out a PR and open the current file on GitHub at the caret line.
- Create a pull request from the branch’s commits and the repository’s template, with a base-branch chooser and an offer to push an unpushed branch.
- A pull request / issue / Actions-runs tool window, with one filter box across all three that matches anything a row shows (number, title, author, branch, state, labels), with a leading
#optional, so42and#42both find PR 42. It opens with focus in the filter and the first row selected;C-n/C-pmove without leaving the box, Down enters the list, Enter opens. Pull requests and issues filter by state (open, closed, merged, all) and “Mine”, and load more on demand. - A status-bar CI checks indicator for the current branch’s pull request. It updates while checks are pending and opens a list of the checks with links and failure logs.
- A failed CI run’s log opens in the Output console with clickable stack frames. Runner paths are mapped back onto your local checkout, so a red build takes you straight to the line. A GitHub tab beside it keeps a transcript of the
ghcommands Editora ran, with their exit codes and durations.
On by default, and invisible until Git support is on, gh is signed in and the repo has an open PR, issue, or workflow run. See the GitHub guide.