Broken Markdown in translated versions of "Searching issues and pull requests" article.
- Linguagem predominante
- TypeScript
- Estrelas
- 20.8k
- Forks
- 68.7k
- Merge médio
- 13h 17min
- PRs com merge (30d)
- 110
Descrição
### Code of Conduct
- [x] I have read and agree to the GitHub Docs project's [Code of Conduct](https://github.com/github/docs/blob/main/.github/CODE_OF_CONDUCT.md)
### What article on docs.github.com is affected?
**Article** link:
https://docs.github.com/fr/search-github/searching-on-github/searching-issues-and-pull-requests
We have this :
Instead of expected well-formed Markdown like this :
### What changes are you suggesting?
Fix the **Markdown** issues in the **French**-translated and **Spanish**-translated versions of the article "[Searching issues and pull requests](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests)", and potentially other languages.
I would have opened a PR, but according to your [translation contribution guidelines](https://github-docs-43.mintlify.app/contributing/translations) this content is not open to direct community contributions.
See the **Additional information** section for more details.
### Additional information
I initially noticed the issue in the French version. I then observed similar problems in other locales, but I haven’t checked all of them. For example, the Spanish version of the article also shows broken Markdown: [Spanish version](https://docs.github.com/es/search-github/searching-on-github/searching-issues-and-pull-requests).
Guia de contribuição
Direção de pesquisa
Comece pelos links dos artigos em francês e espanhol na issue e compare o Markdown renderizado deles com o artigo em inglês. Verifique se outras locales apresentam o mesmo problema; considera-se concluído quando as páginas traduzidas afetadas renderizam Markdown bem formado sem quebrar o conteúdo do artigo.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- markdown
- Domínio
- documentation, localization
- Tipo de issue
- Documentação
- Dificuldade
- 2/5
- Tempo estimado
- 1-3 horas
- Status de atividade
- Pouca atividade
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 65/100