lukov-io/Telegram Message Notify
Sending a Telegram message
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| DEBUG | output fetch responce for api.telegram | — | false |
| SHOULD_BE_SKIPPED | SHOULD_BE_SKIPPED | — | false |
| GITHUB_REPO | GITHUB_REPO | — | — |
| GITHUB_RUN_ID | GITHUB_RUN_ID | — | — |
| TG_BOT_TOKEN | token for telegram bot | — | 1 |
| TG_CHAT_ID | the chat ID that will receive the message | — | 1 |
| TG_TOPIC_ID | the topic of the chat ID that will receive the message | — | — |
| TG_MSG | the message that should be sent | — | — |
| TG_PARSE_MODE | https://core.telegram.org/bots/api#formatting-options | — | html |
| GITHUB_RUNNER_TOKEN | Personal access token (PAT) used to fetch the repository. The PAT is configured with the local git config, which enables your scripts to run authenticated git commands. The post-job step removes the PAT. We recommend using a service account with the least permissions necessary. Also when generating a new PAT, select the least scopes necessary. [Learn more about creating and using encrypted secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets) | — | ${{ github.token }} |
| NEEDS | include only jobs info from job.needs | — | "" |
Outputs
no outputs