Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Melhorar mensagem enviada para Telegram com erro encontrado em arquivo .po pelo linter

Open
  • Is something wrong?
#294 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
documentation, localization

Research direction

Locate the code that formats Telegram notifications for linter errors in .po files, then inspect how the reported file and line are available. The work is done when the message links to the relevant repository line, preferably the msgstr, and provides a Transifex search URL for the target string.

Written by the indexing model from the issue text.

Description

Atualmente, quando o linter encontra um erro no .po, é enviada uma mensagem para o Telegram semelhante a essa

Image

O problema disso é que a linha 1280, deste exemplo, do arquivo não é encontrável pelo Transifex.

Então, seria útil que nessa mensagem viesse a URL para a linha no repositório. No caso, seria

https://github.com/python/python-docs-pt-br/blob/3.14/library/string.po#L1280

Ou com o link permanente:

https://github.com/python/python-docs-pt-br/blob/3dfcdb8c00c002f8667d7478a4aa1625fc9eea1d/library/string.po#L1280

Adicionalmente, talvez ficasse mais claro se a mensagem/link fosse para a linha com a msgstr e não a msgid. E talvez com mais algum texto explicativo.

Adicionalmente 2, enviar um URL para pesquisar no TX por uma strings com o texto da string alvo. Para o exemplo seria:

https://app.transifex.com/python-doc/python-newest/translate/#pt_BR/library--string/592013921?q=text%3A'%3E%3E%3E%20\'{0}%2C%20{1}%2C%20{2}\'.format(\'a\'%2C%20\'b\'%2C%20\'c\')'

Note que foi necessário remover o \n da URL.

Dominant language
Python
Stars
164
Forks
42
Avg merge
12h 39m
Merged PRs (30d)
4

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/python-docs-pt-br

All issues in python/python-docs-pt-br

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.