Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify Markdown vs MarkdownV2 support #45

Open
shardwolfdotnet opened this issue Mar 8, 2022 · 0 comments
Open

Clarify Markdown vs MarkdownV2 support #45

shardwolfdotnet opened this issue Mar 8, 2022 · 0 comments

Comments

@shardwolfdotnet
Copy link

The docs mention MarkdownV2 support, but based on my own tests it appears that only legacy Markdown syntax is supported.

For example, see the following actions snippet:

jobs:
  send_message:
    runs-on: ubuntu-latest
    steps:
      - name: Telegram Message Notify
        uses: appleboy/[email protected]
        with:
          to: ${{ secrets.TELEGRAM_TO }}
          token: ${{ secrets.TELEGRAM_BOT_TOKEN }}
          message: |
            ${{ github.actor }} ${{ github.event.action }} PR ${{ github.event.number }}:
            [_${{ github.event.pull_request.title }}_](${{ github.event.pull_request.html_url }})
          format: markdown

Despite not being escaped, the italicized title didn't work as expected:
image

The markdown style notes mention this:

Entities must not be nested, use parse mode MarkdownV2 instead.

Moreover, drone-telegram seems to indicate markdown (v1) is the supported Markdown flavor - not v2.

Can the docs get updated to indicate which flavor of markdown is actually supported?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant