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

Sourcebot Bug/FR Policy

Aberta
  • Algo errado?
#715 0 comentários 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
1/5
Tempo estimado
Menos de uma hora
Facilidade para iniciantes
20/100
Tipo de issue
Documentação
Clareza
Precisa de esclarecimento
Status de atividade
Estagnada
Domínio
documentation

Direção de pesquisa

No repository file, test, or entry point is named. Treat this as a policy reference rather than a defined implementation task; confirm the relevant documentation location and a specific documentation change before starting.

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

Descrição

Hey everyone!

We care deeply about the feedback you all provide to help make Sourcebot the best dev tool possible. Responding to your bug and FR issues are a core part of this, so we wanted to create this policy to outline our commitments to responding to these requests.

We hope that this policy is fair and makes sense. If it’s not, please let us know how we can do better by replying to this issue.

Bugs

We want Sourcebot to be a high quality dev tool, so we’re committing to a zero-bug policy. As a result, we’re setting the following SLAs:

  • New bugs will be triaged within 8 hours. Triaging a bug means assigning an owner and setting the priority.
  • High priority bugs will be resolved within 2 days and low priority bugs within 7 days.
  • If a bug is too marginal to address the bug will be closed as “not planned”. Please feel free to reopen the bug with additional details if you don’t agree with our decision.
  • If resolving a bug is blocked on the user providing additional information, and they don’t do so within the SLA, the bug will be closed as “not planned”. The bug may be reopened if additional details are provided, in which case the SLA is reset.

Feature Request

Feature requests (FRs) are a core part of how you all can make Sourcebot a better dev tool for everyone. As opposed to bugs, we don’t have strict SLAs for FRs. We review FRs every week and commit to the top ones we can fit in our next engineering sprint.

If you really want an FR to be shipped, please make sure to react to it! That helps us see which FRs are the most requested.

General Inquiry

This could be either a GitHub issue, email, or Slack message that is a general question about the product or docs.

Ideally, 99% of these questions should be answered by our docs. Please check there before submitting a question. We will likely just point you to our docs when answering the question.

In the rare case where our docs don’t answer your question, we will reply within 24 hours and update our docs to include this information for the next user.

Linguagem predominante
TypeScript
Estrelas
3.9k
Forks
374
Merge médio
2d 21h
PRs com merge (30d)
43

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 sourcebot-dev/sourcebot

Todas as issues de sourcebot-dev/sourcebot

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

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