Central repository for Bottles Next
  • Nix 55.6%
  • Just 28%
  • Dockerfile 15.4%
  • Shell 1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-09-25 15:11:32 +05:30
.github ci: enforce AI disclosure 2026-09-13 13:08:16 +02:00
.zed chore: update submodules 2026-08-16 00:40:42 -07:00
build-aux/cpak fix: include protobuf definitions in cpak build 2026-08-16 12:13:03 +02:00
crates chore: Update submodules 2026-09-25 15:11:32 +05:30
.dockerignore feat: add cpak packaging 2026-08-16 12:07:24 +02:00
.gitignore Add Nix flake packaging 2026-06-10 06:01:45 -07:00
.gitmodules chore: Update submodules 2026-08-31 16:22:17 +05:30
AGENTS.md ci: enforce AI disclosure 2026-09-13 13:08:16 +02:00
Cargo.lock chore: Update submodules 2026-09-25 15:11:32 +05:30
Cargo.toml chore: Update submodules 2026-08-31 16:22:17 +05:30
CLAUDE.md ci: enforce AI disclosure 2026-09-13 13:08:16 +02:00
cpak.json chore: pin published image [skip ci] 2026-09-13 11:24:17 +00:00
flake.lock Moved NIX docs out of README and into NIX.md, bumped nix version to new 26.05 and made the flake.nix more userfriendly 2026-06-10 06:01:45 -07:00
flake.nix added automatic submodule initialization 2026-06-10 06:01:45 -07:00
GEMINI.md ci: enforce AI disclosure 2026-09-13 13:08:16 +02:00
justfile chore: Update submodules 2026-08-31 16:22:17 +05:30
LICENSE Initial commit 2025-01-10 13:13:32 +01:00
NIX.md added automatic submodule initialization 2026-06-10 06:01:45 -07:00
README.md ci: enforce AI disclosure 2026-09-13 13:08:16 +02:00

Bottles Next

Central repository for the Bottles Next project.

Usage

Clone the repository:

SSH:

git clone --recursive git@github.com:bottlesdevs/bottles-next.git

HTTPS:

git clone --recursive https://github.com/bottlesdevs/bottles-next.git

Build

To build the project, you can use the just command:

just build

More recipes can be found in the justfile.

Use of Generative AI

Some maintainers use generative AI tools as assistants while working in Bottles, in the spirit of Open Source, we want to be transparent about how, specifically:

  • Code comments and documentation
  • Boilerplate and repetitive code
  • Issue triage (spotting duplicates, outdated reports, grouping similar issues)

Tools vary between contributors (currently mostly Claude and Codex): each AI-assisted commit states the tool and model used in its Assisted-by trailer.

What we don't use it for

Architecture, complex logic, the security and sandboxing model and user experience are designed and written by the maintainers, manually.

Human review

Every line of generated code, documentation and comments are reviewed by a maintainer before it is merged.

Also, starting from the 10th Sep 2026, the following commit pattern must be used for contributions made with or helped with the AI:

feat: add support for X

Assisted-by: <tool>:<model-version>
AI-Scope: what the AI generated in this commit, and the prompt used (or a short summary of it)

Trivial completions (single lines, renames, formatting) don't need to be marked.

Not following this layout will lead to a closed Pull Request.

License

GPL-3.0

Coding agents must also follow AGENTS.md before changing files, creating commits, or opening pull requests.