Files
Kigi-CLI/CONTRIBUTING.md
T
ZacharyZhang-NYandClaude a848b8f06c Move releases, self-update and links to ELY-Open-Source on GitHub
- kigi-env: update_base_url defaults to
  api.github.com/repos/ELY-Open-Source/Kigi-CLI/releases.
- install.sh / install.ps1: resolve releases from the same API.
- /feedback and the no-session feedback fallback open GitHub issues/new;
  /docs opens the README on GitHub.
- SECURITY, NOTICE, AGENTS, CONTRIBUTING: GitHub repo, issues and fork-based
  pull requests replace git.zacharyzhang.com and AGit.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-10-19 19:22:12 -04:00

30 lines
1.0 KiB
Markdown

# Contributing
Kigi is a hard fork of [xai-org/grok-build](https://github.com/xai-org/grok-build)
(which does not accept external contributions). Kigi itself welcomes issues
and pull requests.
## Ground rules
- Toolchain is pinned by `rust-toolchain.toml` (Rust 1.97.0, edition 2024).
- Before opening a PR, make sure the CI gates pass locally:
```sh
cargo check --workspace --all-targets
cargo clippy --workspace --all-targets
cargo fmt --all --check
cargo deny check advisories
```
- No telemetry, analytics, or new outbound endpoints. The closed set of
first-party endpoints lives in `crates/codegen/kigi-env`.
- Upstream syncs are evaluated commit-by-commit and cherry-picked manually;
see the PRD §8.1 policy (`git range-diff` records the adopted set).
## Opening a pull request
Fork [ELY-Open-Source/Kigi-CLI](https://github.com/ELY-Open-Source/Kigi-CLI),
push your branch to the fork, and open a pull request against `main`. Report
bugs and request features on the
[issue tracker](https://github.com/ELY-Open-Source/Kigi-CLI/issues).