Adapt text to new CheckoutPR

Author: koppor

en/contributing/README.md

@@ -12,11 +12,11 @@ Improving on changes in active pull requests is much easier than fixing them lat
 If you are familiar with the command line on your OS, then it is very easy to try out pull requests and give feedback.
 In the following, we try to give a minimal set of installation instructions to be able to run a contribution from a fork.
 
-Required tooling:
+### Required tooling
 
 - [`gg.cmd`](https://github.com/eirikb/gg) - A cross-platform and cross-architecture version manager. Download [`gg.cmd`](https://github.com/eirikb/gg/releases/latest/download/gg.cmd) and store it in your home (or `Downloads`) directory.
 
-Initial setup:
+### Initial setup
 
 - Windows:
   - Open PowerShell
@@ -48,38 +48,37 @@ Initial setup:
 
 Now you are all set: You have a directory `jabref` containing the recent updates and also `gg.cmd` which you will need later for executing a JabRef build.
 
-Try a branch:
+### Try a branch
 
 1. `cd` into the `jabref` source directory: `cd c:\git-repositories\jabref`
-2. Checkout out the pull request: `sh ./gg.cmd gh pr checkout 13182` - where `13182` is the PR number, in this case [pr#13182](https://github.com/JabRef/jabref/pull/13182).
-3. Compile and run JabRef: `sh ./gg.cmd gradle run :jabgui:run` (on Linux and macOS, you need to prefix it with `sh`: `gg.cmd gradle run :jabgui:run`). This will also download the necessary JDK and gradle distribution. On the first run, please give the system enough time to accommodate and wait until the JabRef window launches. Depending on your hardware, this may take minutes.
+2. Checkout out the pull request: `sh ./gg.cmd jbang https://github.com/JabRef/jabref/blob/main/.jbang/CheckoutPR.java 13182` - where `13182` is the PR number, in this case [pr#13182](https://github.com/JabRef/jabref/pull/13182).
 
-On Windows, instead of `sh ./gg.cmd` use `.\gg.cmd`.
-
-Instead of the number, you can also copy and paste the branch identifier output by GitHub.
+   - Instead of the number, you can also copy and paste the branch identifier output by GitHub: `sh ./gg.cmd jbang https://github.com/JabRef/jabref/blob/main/.jbang/CheckoutPR.java Yubo-Cao:walkthrough`.
+     ![pr-13182](../.gitbook/assets/pr-13182.png)
 
-![pr-13182](../.gitbook/assets/pr-13182.png)
+3. Compile and run JabRef: `sh ./gg.cmd gradle run :jabgui:run`. This will also download the necessary JDK and a gradle distribution. On the first run, please give the system enough time to accommodate and wait until the JabRef window launches. Depending on your hardware, this may take minutes.
 
-In this case, you can run `sh ./gg.cmd gh pr checkout Yubo-Cao:walkthrough`
+On Windows, instead of `sh ./gg.cmd` use `.\gg.cmd`.
 
-Alternatives:
+#### Alternatives
 
-1. In case you don't want to use `gg.cmd`:
+1. In case you don't want to use `gg.cmd`: You can install [JBang](https://www.jbang.dev/) for yourself and execute the commands directly.
+2. In case you don't want to use `JBang`:
 
   - You have the project clone ready and have some Java JDK available: In the `JabRef` directory, execute `./gradlew run`.
-  - Install [GitHubCLI](https://cli.github.com/), a command-line client for GitHub by using the installer linked on their [homepage](https://cli.github.com/) or the commands given at the [installation hints](https://github.com/cli/cli#installation).
+  - Install `gh` (the [GitHub CLI](https://cli.github.com/), a command-line client for GitHub) by using the installer linked on their [homepage](https://cli.github.com/) or the commands given at the [installation hints](https://github.com/cli/cli#installation).
 
-2. In case you don't want to use GitHub's `gh` tool: You can use the "usual" `git clone ...`, `git remote add ...`, `git fetch ...`, and `git checkout ...` commands to checkout a pull request from a fork.
+3. In case you don't want to use `gh`: You can use the "usual" `git clone ...`, `git remote add ...`, `git fetch ...`, and `git checkout ...` commands to checkout a pull request from a fork.
 
-**I would like to improve the help page.**
+## I would like to improve the help page
 
 Please see [How to Improve the Help Page](how-to-improve-the-help-page.md)
 
-**I would like to help to translate JabRef to another language.**
+## I would like to help to translate JabRef to another language
 
 We encourage you to read about [translating the JabRef user interface](how-to-translate-the-ui.md).
 
-**I would like to keep Wikipedia pages up-to-date.**
+## I would like to keep Wikipedia pages up-to-date
 
 JabRef improves -- and Wikipedia pages should keep up!
 
@@ -100,16 +99,16 @@ For changes in a specific language, go to the related page, and simply click on
 
 If there is no page for your own language, you can easily create one.
 
-**I have some cool feature requests.**
+## I have some cool feature requests
 
 [Come discuss it!](http://discourse.jabref.org)
 
-**Can I make a donation? How?**
+## Can I make a donation? How?
 
 Donations keep us going! You can use PayPal or bank transfers. Your institution/company can contribute too, through bank transfer for example. All details are provided at [https://donations.jabref.org](https://donations.jabref.org).
 
 Our team consists of volunteers. To provide better support, we are currently trying to get a funded developer on board. Please consider donating money!
 
-**I would like to contribute code. How to?**
+## I would like to contribute code. How to?
 
 Please head to our [Contributing Guide](https://github.com/JabRef/jabref/blob/main/CONTRIBUTING.md#contributing).