apunkt/ktx
1
0
Fork 0
mirror of https://github.com/Kaelio/ktx.git synced 2026-06-07 07:55:13 +02:00
Code Issues Projects Releases Packages Wiki Activity
ktx/CONTRIBUTING.md
Andrey Avtomonov 41f52797de
fix(release): point repository URLs at renamed GitHub repo (#250) 
* fix(release): point repository URLs at renamed GitHub repo

The GitHub repo was renamed from Kaelio/ktx to
Kaelio/ktx-ai-data-agents-context. semantic-release reads repositoryUrl
from package.json's repository field and the @semantic-release/github
plugin failed verifyConditions with EMISMATCHGITHUBURL because it no
longer matched the live clone URL.

Update every Kaelio/ktx reference to the renamed repo: package metadata
(root + CLI repository/bugs/homepage), the codecov upload slugs and
star-history slug in CI, the issue-template and security-advisory links,
the release runbook, and all docs/install commands.

* fix(release): derive semantic-release repositoryUrl from the CI repo

@semantic-release/github exact-matches repositoryUrl against the live
GitHub clone_url (no redirect following), so any repo rename re-breaks the
release when repositoryUrl is the static package.json value.

Derive repositoryUrl from the runner's GITHUB_REPOSITORY/GITHUB_SERVER_URL
so it always tracks the current repo name. A future rename (including back
to Kaelio/ktx) now resolves with no code change. Outside CI the option is
omitted, so semantic-release falls back to package.json as documented.

The package.json repository field stays ktx-ai-data-agents-context as
npm-display metadata, decoupled from the release-time match.
2026-06-01 20:07:24 +02:00

3.9 KiB
Raw Blame History

Contributing to KTX

Thanks for your interest in KTX. This page covers how to contribute and the contributor rewards program. For development setup, repository layout, and verification commands, see the Contributing guide in the docs.

How to contribute

  1. Browse open issues labeled good first issue or help wanted.
  2. Comment on the issue to claim it. A maintainer will confirm scope and assign it to you.
  3. For changes not covered by an existing issue, open one first so we can align on scope before you write code.
  4. Open a pull request that resolves the issue. Keep it focused — one logical change per PR.
  5. Run the relevant checks before requesting review. See the docs contributing page for the right commands per area.

Contributor rewards program

We send merch to contributors whose pull requests get merged. The goal is to thank the people building KTX with us, not to drive volume.

How it works

  1. A maintainer marks an issue reward:eligible when it's ready for an outside contributor.
  2. You open a PR that resolves the issue.
  3. A maintainer reviews and merges.
  4. After merge, the maintainer adds a reward:tier-* label and replies on the PR asking you to email support@kaelio.com with your shipping address, size (if applicable), and a link to the merged PR.
  5. We ship within four weeks.

Reward tiers

Tier Reward Earned by
1 Sticker pack Your first merged PR, any size
2 T-shirt A substantive merged PR: bug fix with a regression test, new docs page, connector test fixture, CLI improvement
3 Hoodie Three or more merged PRs, or one major contribution (new integration, significant feature)

Maintainers decide tier; decisions are final. Tiers do not stack on the same PR.

Eligibility

  • Only merged PRs count. Closed-without-merge or stale PRs do not earn rewards.
  • The GitHub account must be at least 30 days old at the time the PR is opened.
  • The PR must resolve a real issue or measurable improvement.
  • We ship worldwide where customs allow. If we cannot ship to your region we will substitute an equivalent (gift card or digital).

Not eligible

  • Typo-only PRs and whitespace/formatting changes
  • Drive-by style or lint cleanup without prior discussion
  • Mass reformatting or wrapper/abstraction churn
  • AI-generated PRs that do not pass review on their first revision
  • PRs that bundle unrelated changes
  • Anything that would be reverted in code review

We use these rules to keep the program sustainable and to protect the quality of the project. They are not a judgment on contributors — they exist so a small maintainer team can keep saying yes.

Where to ask what

See the Community & Support page for the full guide. The short version:

Code of conduct

KTX follows the Contributor Covenant. Be respectful, assume good intent, and keep discussion focused on the project. Report concerns to the maintainers in Slack or by email at support@kaelio.com.