Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Placeholder image visible behind logos for workshop previews in Slack

Aberta
  • Algo errado?
#2,983 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
rails, ruby
Domínio
web-dev

Direção de pesquisa

Start by reproducing the four workshop links in Slack and Discord, using the screenshots and workshop URLs in the issue to compare the previews. No files or tests are named, so trace how workshop pages generate their preview images and identify why Slack shows a placeholder behind some logos. Done means the affected previews display correctly in Slack without regressing the Discord previews.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Description of the issue 📄

When posting workshop links in slack, a placeholder image is sometimes visible behind the company logo. It appears to be a Slack-only problem. I have pasted links in other places (e.g. Discord) and they have shown up fine.

Screenshots 📷

This image shows the four most recent London workshops (T. Rowe Price, Financial Times, Genomics and Grabyo) pasted into Slack. All except FT demonstrate the problem. It's possible that the FT workshop also has the problem but it is being masked by the dimensions of the logo.

Image

This image shows the above Grabyo workshop pasted into Discord. It does not show the problem described.

Image

Steps to fix 🛠

To do 📋

  • Claim this issue (comment below, or assign yourself if you are part of the codebar org)
  • Fork and clone the repository
  • Update the relevant files. Follow the steps to fix section in this issue.
  • Commit your changes as one commit. Use the title of this issue as your commit message
  • Submit a pull request
  • Mention this issue in the PR description by including it's number
  • Have your pull request reviewed & merged by a codebar team member
Linguagem predominante
Ruby
Estrelas
105
Forks
206
Merge médio
1d 1h
PRs com merge (30d)
78

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de codebar/planner

Todas as issues de codebar/planner

Issues semelhantes

Mais issues de Ruby

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.