Please add a licence file to supabase/splinter

未关闭
#210 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
40/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
领域
documentation

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
PLpgSQL
星标
284
派生
110
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

supabase/splinter 的其他 Issue

查看 supabase/splinter 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。