diff --git a/.github/workflows/greetings.yml b/.github/workflows/greetings.yml
index 341438801..c2c341034 100644
--- a/.github/workflows/greetings.yml
+++ b/.github/workflows/greetings.yml
@@ -11,6 +11,6 @@ jobs:
steps:
- uses: actions/first-interaction@v1
with:
- repo-token: ${{ secrets.ACTION_GREETINGS_TOKEN }}
+ repo-token: ${{ secrets.GITHUB_TOKEN }}
issue-message: "Thanks for opening your first issue in this project! If you haven't already, you can [join our slack](https://docs.google.com/forms/d/e/1FAIpQLSczZbZB9ql_Xl-1uBtmvYmA0fwfm1UX92SyWAdkuMEDfxac5w/viewform) and join the #mobility-database channel to meet our awesome community. Come say hi :wave:!
Welcome to the community and thank you for contributing! :tada:
![](https://media.giphy.com/media/vFKqnCdLPNOKc/giphy.gif)"
pr-message: "Thanks for opening this pull request! You're awesome.
We use [semantic commit messages](https://github.com/electron/electron/blob/main/docs/development/pull-requests.md#commit-message-guidelines) to streamline the release process. Before your pull request can be merged, you should **update your pull request title** to start with a semantic prefix.
Examples of titles with semantic prefixes:
- `fix: Fix wrong countries for some sources`
- `feat: Add Features and Status to MDB Schema [SOURCES]`
- `docs: Improvements to README.md and CONTRIBUTING.md`
If your pull request includes adding or updating a source, make sure to **end your pull request title with \"[SOURCES]\"** so the GitHub workflow runs."