From 8332496b60e5875719fdd8d68194ed8314df6045 Mon Sep 17 00:00:00 2001
From: Jesse Glick <jglick@cloudbees.com>
Date: Fri, 18 Sep 2020 08:35:42 -0400
Subject: [PATCH] Noting gitHubRepo, and a tip about gh pr checks

---
 README.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/README.md b/README.md
index 0bb3239..e73f108 100644
--- a/README.md
+++ b/README.md
@@ -99,6 +99,10 @@ to
 </scm>
 ```
 
+Also replace `jenkinsci/your-repo` occurrences in the `scm` section with a POM property named `gitHubRepo`.
+This will ensure that deployments from forked pull requests will give correct checkout information,
+used for example by `plugin-compat-tester`.
+
 Now run
 
 ```bash
@@ -144,6 +148,13 @@ Your plugin will need to have a `github` field in
 [`repository-permissions-updater`](https://github.com/jenkins-infra/repository-permissions-updater)
 if it does not already.
 
+To check from a shell if your deployment is ready, get the [`gh` CLI](https://cli.github.com/) and try:
+
+```console
+$ gh pr checks | fgrep incrementals | awk '{print $4}'
+https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/ldap/1.27-rc474.9577fe6b8ea6/
+```
+
 To produce equivalent artifacts in your local repository while working offline:
 
 ```bash