appleboy / appleboy/telegram-action
Markdown escaping issue
- Dominant language
- Dockerfile
- Stars
- 1k
- Forks
- 126
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Description
This job step always fails:
```yaml
- name: Send telegram notification
if: ${{always()}}
uses: appleboy/telegram-action@master
with:
to: ${{secrets.TELEGRAM_CHAT}}
token: ${{secrets.TELEGRAM_TOKEN}}
format: markdown
message: |
Test *()
```
Job logs:
```
Run appleboy/telegram-action@master
with:
to: ***
token: ***
format: markdown
message: Test *()
env:
...
/usr/bin/docker run --name dc5057a2652147a674d62abf3a4930e7521c7_f86794 --label 0dc505 --workdir /github/workspace --rm -e ...
2023/10/22 18:39:40 Bad Request: can't parse entities: Can't find end of the entity starting at byte offset 5
```
Should I manually escape chars in `message`?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the GitHub Actions step shown in the issue with the message `Test *()`, then inspect how appleboy/telegram-action passes the message and format to Telegram. Done means the same Markdown message is delivered without Telegram's entity-parsing error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100