Merge #434

434: More details regarding custom registries r=DilumAluthge a=SebastianM-C

I've added some notes documenting some of the configuration details that I've recently learn about on the #github-actions slack channel.

Co-authored-by: Sebastian Micluța-Câmpeanu <[email protected]>

Author: bors[bot]

docs/src/private-registries.md

@@ -10,7 +10,8 @@ After you have the registry configured, you can setup CI using RegistryCI by fol
 
 ## Basic configuration
 
-You will first need to copy the `.ci` folder in the root of the General registry to the root of your own registry. This folder contains some resources required for the RegistryCI package to work and update itself.
+You will first need to copy the `.ci` folder in the root of the General registry to the root of your own registry. This folder contains some resources required for the RegistryCI package to work and update itself. If you do not need AutoMerge support, there is now need to copy the
+`stopwatch.jl` file in the `.ci` folder.
 
 Next, you will need to copy the `ci.yml` and `update_manifest.yml` workflow files.
 
@@ -68,3 +69,21 @@ Most importantly, the following should be changed
 registry = "MyOrg/MyRegistry",
 authorized_authors = String["TrustedUser"],
 ```
+
+You will also have to make the following change in `.ci/stopwatch.jl`
+
+```diff
+- registry = GitHub.Repo("JuliaRegistries/General")
++ registry = GitHub.Repo("MyOrg/MyRegistry")
+```
+
+## Note regarding private registries
+
+In the case of a private registry, you might get permission errors when executing the `instantiate.sh` script.
+In that case you will also have to add the following
+```diff
+  - run: chmod 400 .ci/Project.toml
+  - run: chmod 400 .ci/Manifest.toml
++ - run: chmod +x .ci/instantiate.sh
+```
+in `ci.yml` and also `TagBotTriggers.yml` and `automerge.yml` (in which the above appears twice) files if those features are used.