Skip to content

Commit 51d562c

Browse files
authored
Document how to disable workflows in forks (#14834)
1 parent 1056373 commit 51d562c

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

CONTRIBUTING.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,18 @@ the file name to stay consistent across versions. To do so, add the following to
6262
removeJarVersionNumbers=true
6363
```
6464

65+
## Working with fork repositories
66+
67+
If you forked this repository, some GitHub Actions workflows may fail due to missing secrets or permissions. To avoid unnecessary workflow failure notifications:
68+
69+
### Disabling GitHub Actions in your fork
70+
71+
**Option 1: Disable all workflows** - Go to Settings > Actions > General, select "Disable actions", and save
72+
73+
**Option 2: Disable specific workflows** - Go to Actions tab, click a workflow, click "..." menu, and select "Disable workflow"
74+
75+
Either option still allows you to contribute via pull requests to the main repository.
76+
6577
## IntelliJ setup and troubleshooting
6678

6779
See [IntelliJ setup and troubleshooting](docs/contributing/intellij-setup-and-troubleshooting.md)
@@ -99,7 +111,7 @@ See [Understanding Muzzle](docs/contributing/muzzle.md)
99111
The build logs are very long and there is a lot of parallelization, so the logs can be hard to
100112
decipher, but if you expand the "Build scan" step, you should see something like:
101113

102-
```
114+
```text
103115
Run cat build-scan.txt
104116
https://gradle.com/s/ila4qwp5lcf5s
105117
```

0 commit comments

Comments
 (0)