Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add docs around how Sourcebot handles rate-limiting against code hosts

Abierto
#317 1 comentario 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
38/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
github

Línea de trabajo

Start by reading the linked GitHub REST API rate-limit documentation and Discussion #316, including its concerns about PAT usage and account suspension. Identify where the project’s documentation describes code-host access, then add accurate guidance on Sourcebot’s rate-limiting behavior, warnings, and relevant workarounds; done means the risks and controls are clearly documented.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

documentation

See:

Discussed in https://github.com/sourcebot-dev/sourcebot/discussions/316

Originally posted by dsculptor May 27, 2025

Excessive PAT token usage can suspend your github account!

One of my colleagues had her github account suspended. The most likely reason we think is because of excessive API usage via her PAT token in our sourcebot instance. Our self-hosted instance had 15+ public repos indexed (mainly AI SDKs).

Although, github has not shared any details on the exact reasons for suspension; everything else about her account / activity had been normal since forever.

💡 Ideas
  • Would request soucebot team to put reasonable warnings e.g link to section H in the docs for using PATs.
  • Suggest workarounds.
  • Rate limiting / controls on pull frequency can be added as well.

Github Terms Section H

Screenshot 2025-05-27 at 2 57 52 AM

Lenguaje dominante
TypeScript
Estrellas
3.9k
Forks
374
Merge medio
21 h 18 min
PR fusionados (30 d)
39

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de sourcebot-dev/sourcebot

Todos los issues de sourcebot-dev/sourcebot

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.