Please add a licence file to supabase/splinter

Abierto
#210 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
40/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo

Línea de trabajo

The missing piece is a LICENSE file at the repository root, and the README licence badge links to it and currently returns a 404. Check the README badge line and confirm the root has no licence file. Adding the file needs a licence choice from the maintainers first, so ask them which licence applies before writing anything. Done means the file exists with the agreed licence text and the badge link resolves.

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

Descripción

Hello Supabase team,

Thank you for splinter. It is a clear and useful set of database checks, and we have learned a lot from how it explains each lint.

We wanted to use it in our CI, but the repository does not state a licence. GitHub shows no licence for it, there is no LICENSE file at the root, and the licence badge in the README links to a LICENSE file that returns a 404.

Without a licence, we read the default as "all rights reserved", so we cannot copy or run the SQL in our own pipeline, and we have written our own checks for now.

Could you add a licence file to the repository (for example Apache 2.0, matching many other Supabase projects), or tell us in writing which licence applies? If it is simply a missing file, a one-line fix would help everyone who wants to run splinter outside the Supabase dashboard.

Thank you for your time and for the work on splinter.

Kind regards,
Johan Matsgård
Matsgard Group

Lenguaje dominante
PLpgSQL
Estrellas
284
Forks
110
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

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 supabase/splinter

Todos los issues de supabase/splinter

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.