Skip to content

Commit 2f10d79

Browse files
authored
Merge pull request #1463 from tbogosavljevic/patch-3
Slack notifications: clarifying confusing information
2 parents 08d7016 + c831b91 commit 2f10d79

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/essentials/slack-notifications.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -62,10 +62,10 @@ $ sem create notifications new-releases \
6262
--slack-channels "#dev-team,#qa-team"
6363
```
6464

65-
## Filtering by project, branch, and pipeline name
65+
## Filtering by project, branch, and pipeline YAML file name
6666

6767
When creating a notification, you can specify filters for project, branch, and
68-
pipeline names.
68+
pipeline YAML file names.
6969

7070
For example, to send notifications for the `master` and `staging` branches, use
7171
the following command:
@@ -90,7 +90,7 @@ Regex matches must be wrapped in forward slashes (e.g. `/.*/`). Specifying a
9090
branch name without slashes (e.g. `.*`) will execute a direct equality
9191
match.
9292

93-
Matching can be specified for project and pipeline names as well. For example,
93+
Matching can be specified for project and pipeline YAML file names as well. For example,
9494
if you want to get notified for every notification on a project that matches
9595
`/.*-api$/` on the master branch when the `prod.yml` pipeline is executed, use
9696
the following command:

0 commit comments

Comments
 (0)