mirror of
https://github.com/SonarSource/sonarqube-scan-action.git
synced 2025-12-16 10:58:28 +00:00
Update README.md
Users unfamiliar with GitHub actions just copy the pipeline snippets and wonder why the analysis does not trigger. Let's make sure it does.
This commit is contained in:
parent
50d5d98163
commit
1da11d47fb
1 changed files with 4 additions and 2 deletions
|
|
@ -28,11 +28,13 @@ The workflow YAML file will usually look something like this:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
on:
|
on:
|
||||||
# Trigger analysis when pushing in master or pull requests, and when creating
|
# Trigger analysis when pushing to your main branches, and when creating a pull request.
|
||||||
# a pull request.
|
|
||||||
push:
|
push:
|
||||||
branches:
|
branches:
|
||||||
|
- main
|
||||||
- master
|
- master
|
||||||
|
- develop
|
||||||
|
- 'releases/**'
|
||||||
pull_request:
|
pull_request:
|
||||||
types: [opened, synchronize, reopened]
|
types: [opened, synchronize, reopened]
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue