Some glue between embark and a number of version control packages. As it’s (currently) quite simple, there’s not much to document. As that changes, so will this.
Currently provides targets and actions for:
- Magit (forge)
- smerge-mode
- code-review
All of which are considered dependencies, but as the package grows they will become optional (if I did that now, it wouldn’t do anything!)
In the context of Magit, Issues and Pull Requests are both marked as “topics”, and are referred to as such in the codebase to denote actions that apply to both. For example, setting the title of an Issue or a Pull Request is fundamentally the same operation, however Issues can’t be merged.
So the “topic” actions are defined as actions that would apply to both Issues and Pull Requests, with both also having their own set of actions to act on.
Clone the repo, add to your load-path
Install using your favourite package manager
Append the following to the corresponding file:
(package! embark-vc)(use-package! embark-vc
:after embark)Currently all it really does is create some targets and add some wrapped verisons of existing functions.
Keymap applies to both Pull Requests and Issues, so won’t be duplicated there
| key | action |
|---|---|
y | forge-copy-url-at-point-as-kill |
s | embark-vc-edit-topic-state |
t | embark-vc-edit-topic-title |
l | embark-vc-edit-topic-labels |
Only list actions that are relevant to just Pull Requests
| key | action |
|---|---|
c | embark-vc-checkout-branch |
b | forge-browse-pullreq |
r | embark-vc-start-review |
n | forge-merge |
Only list actions that are relevant to just Issues
| key | action |
|---|
Only list actions that are relevant to Commits
| key | action |
|---|---|
b | forge-browse-commit |
Only list actions that are relevant to Merge Conflicts
| key | action |
|---|---|
t | smerge-keep-upper |
b | smerge-keep-lower |
a | smerge-keep-all |
d | smerge-ediff |