From fb4e58111e148d4927532b62b217597d36da2495 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Codru=C8=9B=20Constantin=20Gu=C8=99oi?= Date: Sun, 20 Jan 2019 22:45:54 +0200 Subject: [PATCH] Fix link to forge setup instructions --- CONTRIBUTING.org | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.org b/CONTRIBUTING.org index 1a75d7bb9e4e..914eeb518c53 100644 --- a/CONTRIBUTING.org +++ b/CONTRIBUTING.org @@ -270,11 +270,10 @@ changes, your review is very valuable in these cases as well! ** Using Magit to quickly test PRs It is possible to manage PRs directly inside the Magit status buffer ~SPC g s~. First add the =github= layer to your dotfile which will pull the package -=forge=. Once installed you need to set it up with a [[GitHub personal access -token][https://magit.vc/manual/ghub/Getting-Started.html#Getting-Started]] after -which you can execute ~M-x forge-pull~. It will fetch all the PRs which may take -a few seconds as we have lot of PRs. Note also that all your Magit actions will -get some additional delay due to the refresh of the PRs list. +=forge=. Once installed you need to set it up with a [[https://magit.vc/manual/ghub/Getting-Started.html#Getting-Started][GitHub personal access +token]] after which you can execute ~M-x forge-pull~. It will fetch all the PRs +which may take a few seconds as we have lot of PRs. Note also that all your +Magit actions will get some additional delay due to the refresh of the PRs list. Now, from the magit status buffer you can: - checkout a PR with ~b y~ and searching it by name or ID