Skip to content

Document how to disable workflows in forks #14834

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 30, 2025
Merged

Document how to disable workflows in forks #14834

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
433587e
Document how to disable workflows in forks
trask Sep 29, 2025
dbc1e79
up
trask Sep 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 19 additions & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,24 @@ the file name to stay consistent across versions. To do so, add the following to
removeJarVersionNumbers=true
```

## Working with fork repositories

If you forked this repository, some GitHub Actions workflows may fail due to missing secrets or permissions. To avoid unnecessary notifications:

### Disabling GitHub Actions in your fork

#### Option 1: Disable all workflows

1. Go to your fork's "Actions" tab
2. Click "Disable Actions"

#### Option 2: Disable specific workflows

1. Go to your fork's "Actions" tab
2. Use workflow-specific controls to disable problematic ones

Both approaches allow normal contribution via pull requests to the main repository.

## IntelliJ setup and troubleshooting

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

```
```text
Run cat build-scan.txt
https://gradle.com/s/ila4qwp5lcf5s
```
Expand Down
Loading