Add Telegram Bot message reactions

[aviadlevy]

Breaking change

Proposed change

Add message reaction to Telegram bot

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Adding 'set_message_reaction' action home-assistant.io#39430
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hi @aviadlevy

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

Stale

[hanwg]

I tested this and it works fine.

[hanwg]

@aviadlevy for the merge conflict, I think you only need to move your test to the end of the test_telegram_bot.py file.

[aviadlevy]

@aviadlevy for the merge conflict, I think you only need to move your test to the end of the test_telegram_bot.py file.

I just rebased a few hours ago due to conflicts.
At least every rebase brings this MR one step closer to review and merge. 🤞

[abmantis]

Just 2 minor changes, but otherwise LGTM

[abmantis]

Oh by the way, please avoid rebasing after getting a review and use merge instead. It makes it easier to review changes since Github does not deal with git history changes well for partial reviews.

[aviadlevy]

Oh by the way, please avoid rebasing after getting a review and use merge instead. It makes it easier to review changes since Github does not deal with git history changes well for partial reviews.

Thanks for the review!
Just to confirm - does that mean I should avoid amending commits too, and instead push every change as a new commit?

[abmantis]

Oh by the way, please avoid rebasing after getting a review and use merge instead. It makes it easier to review changes since Github does not deal with git history changes well for partial reviews.

Thanks for the review! Just to confirm - does that mean I should avoid amending commits too, and instead push every change as a new commit?

Yes. All commits will be squashed when merging to dev, so it is fine to have multiple commits in the PR.

[abmantis]

Thanks!

[abmantis]

Thanks @aviadlevy !

By the way, for future PRs I would suggest avoiding adding unrelated changes (like updating other tests) in the same PR, as noted in https://developers.home-assistant.io/docs/review-process#creating-the-perfect-pr