Skip to content

Releases: GokulDas027/TelegramBridge

Telegram Bridge

03 Oct 18:07
6846498
Compare
Choose a tag to compare

Telegram Bridge

This is a GitHub Action plugin to notify about the changes in GitHub to Telegram Chat via Bot. This could highly help in increasing the development pace.

What's Updated?

Fixed Markdown Parse Errors from the previous release. (v1.1)

What all can this do ?

If you're using the provided main.yaml (recommended)

Will Notify about :

  • Pushes
  • Pull Requests (opened, closed, edited, ready_for_review, review_requested, reopened)
  • Pull Request Review Comments (created)
  • Issues (opened, edited, pinned, closed, reopened, assigned, labeled)
  • Issue Comments (created)

the limits are not the boundary, but set for reducing the message bombarding, and it can be easily changed at the main.yaml file at your repository. This could help Action Triggers Docs.

How to Use this ?

This will be available as a plugin here.

Or can be used through this main.yaml file
> move it to /.github/workflows/main.yml

Connect it to a Telegram bot.

  • Token is the token of the Bot given by BotFather
  • Id is the Channel id or your user id, depends on how you need the message to be delivered.

Check here for step by step instructions

Telegram Bridge

10 Jul 07:34
3473eba
Compare
Choose a tag to compare

Telegram Bridge

This is a GitHub Action plugin to notify about the changes in GitHub to Telegram Chat via Bot. This could highly help in incresing the development pace.

What's Updated?

Fixed Markdown Parse Error for Underscore("-") from the previous release. (v1.0.c) by @ashpooljh

What all can this do ?

If you're using the provided main.yaml (recommended)

Will Notify about :

  • Pushes
  • Pull Requests (opened, closed, edited, ready_for_review, review_requested, reopened)
  • Pull Request Review Comments (created)
  • Issues (opened, edited, pinned, closed, reopened, assigned, labeled)
  • Issue Comments (created)

the limits are not the boundary, but set for reducing the message bombarding, and it can be easily changed at the main.yaml file at your repository. This could help Action Triggers Docs.

How to Use this ?

This will be available as a plugin here.

Or can be used through this main.yaml file
> move it to /.github/workflows/main.yml

Connect it to a Telegram bot.

  • Token is the token of the Bot given by BotFather
  • Id is the Channel id or your user id, depends on how you need the message to be delivered.

Check here for step by step instructions

Telegram Bridge

04 Jun 13:52
9b5e613
Compare
Choose a tag to compare

Telegram Bridge

This is a GitHub Action plugin to notify about the changes in GitHub to Telegram Chat via Bot. This could highly help in incresing the development pace.

What's Updated?

Fixed Markdown Parse Error for Underscore("_") from the previous release. (v1.0.b)

What all can this do ?

If you're using the provided main.yaml (recommended)

Will Notify about :

  • Pushes
  • Pull Requests (opened, closed, edited, ready_for_review, review_requested, reopened)
  • Pull Request Review Comments (created)
  • Issues (opened, edited, pinned, closed, reopened, assigned, labeled)
  • Issue Comments (created)

the limits are not the boundary, but set for reducing the message bombarding, and it can be easily changed at the main.yaml file at your repository. This could help Action Triggers Docs.

How to Use this ?

This will be available as a plugin here.

Or can be used through this main.yaml file
> move it to /.github/workflows/main.yml

Connect it to a Telegram bot.

  • Token is the token of the Bot given by BotFather
  • Id is the Channel id or your user id, depends on how you need the message to be delivered.

Check here for step by step instructions

Telegram Bridge

08 Dec 11:51
9da206b
Compare
Choose a tag to compare

Telegram Bridge

This is a GitHub Action plugin to notify about the changes in GitHub to Telegram Chat via Bot. This could highly help in incresing the development pace.

Fixed bug from the previous release. (v1.0.a)

What all can this do ?

If you're using the provided main.yaml (recommended)

Will Notify about :

  • Pushes
  • Pull Requests (opened, closed, edited, ready_for_review, review_requested, reopened)
  • Pull Request Review Comments (created)
  • Issues (opened, edited, pinned, closed, reopened, assigned, labeled)
  • Issue Comments (created)

the limits are not the boundary, but set for reducing the message bombarding, and it can be easily changed at the main.yaml file at your repository. This could help Action Triggers Docs.

How to Use this ?

This will be available as a plugin here.

Or can be used through this main.yaml file
> move it to /.github/workflows/main.yml

Connect it to a Telegram bot.

  • Token is the token of the Bot given by BotFather
  • Id is the Channel id or your user id, depends on how you need the message to be delivered.

Check here for step by step instructions

Telegram Bridge

07 Dec 15:02
Compare
Choose a tag to compare

Telegram Bridge

This is a GitHub Action plugin to notify about the changes in GitHub to Telegram Chat via Bot. This could highly help in incresing the development pace.

What all can this do ?

Notify about :

  • Pushes
  • Pull Requests (opened, closed, edited, ready_for_review, review_requested, reopened)
  • Pull Request Review Comments (created)
  • Issues (opened, edited, pinned, closed, reopened, assigned, labeled)
  • Issue Comments (created)

This above mentioned is the case when using the provided main.yaml file, it can be customized. the limits are not the boundary, but set for reducing the message bombarding, and it can be easily changed at the main.yaml file at your repository. This could help Action Triggers Docs.

How to Use this ?

can be used through this main.yaml file
> move it to /.github/workflows/main.yml

Telegram Bridge

07 Dec 13:40
485773e
Compare
Choose a tag to compare

Telegram Bridge

This is a GitHub Action plugin to notify about the changes in GitHub to Telegram Chat via Bot. This could highly help in increasing the development pace.

What all can this do ?

Notify about :

  • Pushes
  • Pull Requests (opened, closed, edited, ready_for_review, review_requested, reopened)
  • Pull Request Review Comments (created)
  • Issues (opened, edited, pinned, closed, reopened, assigned, labeled)
  • Issue Comments (created)

the limits are not the boundary, but set for reducing the message bombarding, and it can be easily changed at the main.yaml file at your repository. This could help Action Triggers Docs.