feat: add GitBook deprecation banner to every page#45
Merged
Conversation
📝 WalkthroughWalkthroughAdds an idempotent Node.js script to insert a standardized DEPRECATION-BANNER and applies that banner to 61 Markdown docs, directing readers to docs.gokite.ai and the gokite-ai/kite-docs issue tracker. ChangesDocumentation Deprecation Banner Rollout
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRsPoem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
🧹 Nitpick comments (4)
scripts/add-deprecation-banner.mjs (1)
62-69: ⚡ Quick winConsider more granular error handling for individual file operations.
Currently, if any single file read or write fails (e.g., due to permissions), the entire script terminates via the
catchhandler on line 74. For a bulk-update script operating on 61 files, it would be more resilient to log individual failures and continue processing remaining files.♻️ Proposed enhancement with per-file error handling
let updated = 0; + let failed = 0; for (const rel of files) { const full = path.join(root, rel); - const src = await readFile(full, 'utf8'); - const next = applyBanner(src); - if (next !== src) { - await writeFile(full, next, 'utf8'); - updated += 1; + try { + const src = await readFile(full, 'utf8'); + const next = applyBanner(src); + if (next !== src) { + await writeFile(full, next, 'utf8'); + updated += 1; + } + } catch (err) { + console.error(`Failed to process ${rel}:`, err.message); + failed += 1; } } - console.log(`Updated ${updated}/${files.length} files.`); + console.log(`Updated ${updated}/${files.length} files${failed > 0 ? ` (${failed} failed)` : ''}.`); + if (failed > 0) process.exit(1);🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@scripts/add-deprecation-banner.mjs` around lines 62 - 69, Wrap the per-file work inside the for loop (where files, rel, full, src, next, updated are used) in its own try/catch so a single readFile/applyBanner/writeFile failure does not abort the whole run; specifically, inside the loop around the calls to readFile(full, 'utf8'), applyBanner(src) and writeFile(full, next, 'utf8') catch the error, log a clear message that includes the file path (full) and the error, and then continue to the next iteration—keep the outer catch for unexpected fatal errors but make the loop resilient by handling per-file errors locally.kite-chain/10-layerzero-kite-integration/README.md (1)
1-5: 💤 Low valueConsider adding a timeline to the deprecation notice.
The deprecation banner mentions "at cutover" but doesn't specify when this will occur. Consider adding an approximate date or timeline to help users plan accordingly.
Example:
-**⚠️ These docs are moving to a new home.** Preview the new site at [docs-preview.gokite.ai](https://docs-preview.gokite.ai). At cutover, this site will redirect there automatically. +**⚠️ These docs are moving to a new home.** Preview the new site at [docs-preview.gokite.ai](https://docs-preview.gokite.ai). This site will redirect there automatically on [DATE/Q3 2026].🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@kite-chain/10-layerzero-kite-integration/README.md` around lines 1 - 5, Update the deprecation banner block (the <!-- DEPRECATION-BANNER:START --> ... {% endhint %} <!-- DEPRECATION-BANNER:END --> section) to include an approximate cutover timeline or date; edit the hint content string that currently reads "**⚠️ These docs are moving to a new home.** Preview the new site..." to append a short sentence like "Expected cutover: <approximate date or timeframe> (subject to change)" or similar, so users can plan ahead while keeping the existing link and issue guidance intact.kite-chain/4-building-dapps/voting-dapp.md (1)
7-7: ⚡ Quick winConsider adding a cutover timeline for user clarity.
The banner states "At cutover, this site will redirect there automatically" but doesn't specify when cutover will occur. Consider adding a target date or timeline (e.g., "Cutover planned for June 2026") to help users plan accordingly.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@kite-chain/4-building-dapps/voting-dapp.md` at line 7, Update the banner text that currently reads "At cutover, this site will redirect there automatically" to include a clear cutover timeline or target date (e.g., "Cutover planned for June 2026" or "Cutover targeted Q2 2026") so users can plan; locate and modify the string in voting-dapp.md where the banner is defined and ensure the added timeline is concise and visible alongside the existing redirect message.kite-chain/9-gasless-integration/README.md (1)
2-4: ⚡ Quick winConsider adding a cutover date or timeline for clarity.
The banner states "at cutover, this site will redirect there automatically" but doesn't specify when cutover will occur. Users might benefit from knowing whether to expect this change in days, weeks, or months, or at minimum, where they can find that information.
💡 Example with timeline information
{% hint style="warning" %} -**⚠️ These docs are moving to a new home.** Preview the new site at [docs-preview.gokite.ai](https://docs-preview.gokite.ai). At cutover, this site will redirect there automatically. File issues against [gokite-ai/kite-docs](https://github.com/gokite-ai/kite-docs). +**⚠️ These docs are moving to a new home.** Preview the new site at [docs-preview.gokite.ai](https://docs-preview.gokite.ai). This site will redirect there automatically on [DATE]. File issues against [gokite-ai/kite-docs](https://github.com/gokite-ai/kite-docs). {% endhint %}Or if the date is not yet determined:
{% hint style="warning" %} -**⚠️ These docs are moving to a new home.** Preview the new site at [docs-preview.gokite.ai](https://docs-preview.gokite.ai). At cutover, this site will redirect there automatically. File issues against [gokite-ai/kite-docs](https://github.com/gokite-ai/kite-docs). +**⚠️ These docs are moving to a new home.** Preview the new site at [docs-preview.gokite.ai](https://docs-preview.gokite.ai). This site will redirect there automatically in the coming weeks. File issues against [gokite-ai/kite-docs](https://github.com/gokite-ai/kite-docs). {% endhint %}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@kite-chain/9-gasless-integration/README.md` around lines 2 - 4, The warning banner (the `{% hint style="warning" %}` block) lacks a cutover date or timeline; update that banner to include either a specific cutover date, an estimated timeframe (e.g., "expected in Q3 2026"), or a pointer to where users can track the cutover status (e.g., a "Cutover status" link or note like "date TBD — subscribe at ..."); modify the README.md banner text accordingly so it clearly communicates timing or where to find updates.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@integration-guide/case-study-app-store.md`:
- Around line 1-6: Update the DEPRECATION-BANNER block to include an approximate
cutover timeline so readers can plan; edit the existing hint block (the /**⚠️
These docs are moving to a new home.** message inside <!--
DEPRECATION-BANNER:START --> ... :END -->) to append a short date or timeframe
(e.g., "Expected cutover: Month Year" or "Read-only after DATE") and a note
about when links/redirects will activate and where to file issues, keeping the
warning style consistent and concise.
In `@integration-guide/workflow-agent-builders.md`:
- Around line 1-6: The deprecation banner uses GitBook hint templating (`{% hint
style="warning" %}...{% endhint %}`) and points to potentially unreachable
targets; replace the GitBook-specific block with a plain Markdown warning (e.g.,
a bold "⚠️ These docs are moving..." paragraph or a standard blockquote) so it
renders everywhere, and update the two links (`docs-preview.gokite.ai` and
`github.com/gokite-ai/kite-docs`) to either publicly reachable URLs or mark them
as internal/private with a parenthetical note (e.g., "(internal preview)" or
"(private repo)") so readers know the access expectations.
In `@kite-agent-passport/beginner-setup.md`:
- Around line 5-9: Update the DEPRECATION-BANNER block in the
kite-agent-passport/beginner-setup.md file to replace the unreachable/404 links:
change the preview docs URL `https://docs-preview.gokite.ai` to a working docs
URL (e.g., `https://docs.gokite.ai`) and replace the broken repo link
`https://github.com/gokite-ai/kite-docs` with a valid repository or organization
URL (e.g., `https://github.com/gokite-ai` or the correct docs repo); ensure the
{% hint %} banner text and links are updated together so the banner points to
reachable targets and add a short TODO comment in the banner referencing the
correct repo if the exact repo URL is unknown.
In `@kite-chain/10-layerzero-kite-integration/README.md`:
- Around line 1-5: Update the deprecation banner links in README.md to point to
valid, reachable targets: replace the preview URL
`https://docs-preview.gokite.ai` with the correct preview host (or remove the
link) and update the repository reference `gokite-ai/kite-docs` to the actual
GitHub repo name (or remove the link) so both links resolve; edit the
HTML/Markdown block containing the banner (the <!-- DEPRECATION-BANNER:START -->
... {% endhint %} block) to use the corrected URLs or plain text if the targets
don't exist.
In `@kite-chain/4-building-dapps/voting-dapp.md`:
- Line 7: Update the deprecation banner text to use reachable URLs: replace the
preview site URL `https://docs-preview.gokite.ai` with the public site
`https://docs.gokite.ai` and update the GitHub repo link from
`https://github.com/gokite-ai/kite-docs` to
`https://github.com/gokite-ai/developer-docs` so the banner's links resolve
correctly (look for the banner string "**⚠️ These docs are moving to a new
home.** Preview the new site at" and update the two URLs accordingly).
In `@scripts/add-deprecation-banner.mjs`:
- Line 45: The RegExp construction directly interpolates BANNER_START and
BANNER_END into new RegExp(...) which is fragile; add an escape helper (e.g.,
escapeRegExp) and use it to escape BANNER_START and BANNER_END before building
the pattern (or build the regex with explicit escaped literals) so the pattern
becomes escapeRegExp(BANNER_START) + '[\\s\\S]*?' + escapeRegExp(BANNER_END) +
'\\n*'; update the call site that currently uses new
RegExp(`${BANNER_START}[\\s\\S]*?${BANNER_END}\\n*`) to use the escaped values
instead.
---
Nitpick comments:
In `@kite-chain/10-layerzero-kite-integration/README.md`:
- Around line 1-5: Update the deprecation banner block (the <!--
DEPRECATION-BANNER:START --> ... {% endhint %} <!-- DEPRECATION-BANNER:END -->
section) to include an approximate cutover timeline or date; edit the hint
content string that currently reads "**⚠️ These docs are moving to a new home.**
Preview the new site..." to append a short sentence like "Expected cutover:
<approximate date or timeframe> (subject to change)" or similar, so users can
plan ahead while keeping the existing link and issue guidance intact.
In `@kite-chain/4-building-dapps/voting-dapp.md`:
- Line 7: Update the banner text that currently reads "At cutover, this site
will redirect there automatically" to include a clear cutover timeline or target
date (e.g., "Cutover planned for June 2026" or "Cutover targeted Q2 2026") so
users can plan; locate and modify the string in voting-dapp.md where the banner
is defined and ensure the added timeline is concise and visible alongside the
existing redirect message.
In `@kite-chain/9-gasless-integration/README.md`:
- Around line 2-4: The warning banner (the `{% hint style="warning" %}` block)
lacks a cutover date or timeline; update that banner to include either a
specific cutover date, an estimated timeframe (e.g., "expected in Q3 2026"), or
a pointer to where users can track the cutover status (e.g., a "Cutover status"
link or note like "date TBD — subscribe at ..."); modify the README.md banner
text accordingly so it clearly communicates timing or where to find updates.
In `@scripts/add-deprecation-banner.mjs`:
- Around line 62-69: Wrap the per-file work inside the for loop (where files,
rel, full, src, next, updated are used) in its own try/catch so a single
readFile/applyBanner/writeFile failure does not abort the whole run;
specifically, inside the loop around the calls to readFile(full, 'utf8'),
applyBanner(src) and writeFile(full, next, 'utf8') catch the error, log a clear
message that includes the file path (full) and the error, and then continue to
the next iteration—keep the outer catch for unexpected fatal errors but make the
loop resilient by handling per-file errors locally.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: d7f05e03-2797-4a29-ad54-363c548361b5
📒 Files selected for processing (66)
README.mdchangelog/2026/2026-05-19-backend-v1-1-0.mdchangelog/2026/2026-05-19-cli-v1-3-4.mdchangelog/2026/2026-05-19-skills-v0-9-1.mdchangelog/2026/2026-05-19-web-v1-2-0.mdchangelog/README.mddev/README.mddocs/STYLING_GUIDE.mdget-started-why-kite/tokenomics.mdget-started/README.mdget-started/architecture-and-design-pillars.mdget-started/core-concepts-and-terminology.mdget-started/introduction-and-mission.mdget-started/key-use-cases-and-players.mdget-started/whitepaper-references.mdintegration-guide/README.mdintegration-guide/api-agent-builder-guide.mdintegration-guide/api-merchants-payment-providers.mdintegration-guide/api-references.mdintegration-guide/case-study-app-store.mdintegration-guide/sdk-api-overview-for-developers/README.mdintegration-guide/sdk-api-overview-for-developers/agent-builder-guide.mdintegration-guide/sdk-api-overview-for-developers/merchant-integration-guide.mdintegration-guide/workflow-agent-builders.mdintegration-guide/workflow-merchants-payment-providers.mdintegration-guide/workflow-overview.mdintegration-guide/workflow-overview/README.mdintegration-guide/workflow-overview/workflow-a-agent-builders.mdintegration-guide/workflow-overview/workflow-b-merchants-and-payment-providers.mdkite-agent-passport/README.mdkite-agent-passport/add-kite-tokens-external-wallet.mdkite-agent-passport/beginner-setup.mdkite-agent-passport/cli-reference.mdkite-agent-passport/funding.mdkite-agent-passport/service-provider-guide.mdkite-chain/1-getting-started/README.mdkite-chain/1-getting-started/faqs.mdkite-chain/1-getting-started/network-information.mdkite-chain/1-getting-started/tools.mdkite-chain/10-layerzero-kite-integration/README.mdkite-chain/11-goldsky-kite-integration/README.mdkite-chain/12-lucid-kite-integration/README.mdkite-chain/2-fundamentals/README.mdkite-chain/2-fundamentals/blockchain-fundamentals.mdkite-chain/2-fundamentals/smart-contract-basics.mdkite-chain/3-developing/README.mdkite-chain/3-developing/counter-smart-contract-hardhat.mdkite-chain/3-developing/counter-smart-contract-remix.mdkite-chain/3-developing/setup-environment.mdkite-chain/3-developing/smart-contracts-list.mdkite-chain/3-developing/voting-smart-contract.mdkite-chain/4-building-dapps/README.mdkite-chain/4-building-dapps/counter-dapp.mdkite-chain/4-building-dapps/token-minter.mdkite-chain/4-building-dapps/voting-dapp.mdkite-chain/5-advanced/README.mdkite-chain/5-advanced/account-abstraction-sdk.mdkite-chain/5-advanced/multisig-wallet.mdkite-chain/6-reference.mdkite-chain/7-kite-node/README.mdkite-chain/7-kite-node/mainnet-network-information.mdkite-chain/7-kite-node/mainnet-node-operations.mdkite-chain/8-kite-stablecoin/stablecoin-gasless-transfer.mdkite-chain/9-gasless-integration/README.mdkite-chain/mica-whitepaper.mdscripts/add-deprecation-banner.mjs
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
.github/workflows/changelog-commands.yml (1)
3-11:⚠️ Potential issue | 🔴 Critical | ⚡ Quick winFix changelog-commands.yml trigger/context mismatch (manual dispatch won’t run commands).
workflow_dispatchis the only trigger (line 3), but both the job and steps are gated ongithub.event.issueandgithub.event.comment.body(lines 7-11, plus stepif:guards). Those fields only exist forissue_commentevents, so a manual dispatch will skip the job and never execute/regenerateor/skip.🔧 Proposed fix: add the missing issue_comment trigger (or refactor the conditions)
on: workflow_dispatch: + issue_comment: + types: [created]🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/changelog-commands.yml around lines 3 - 11, The workflow currently only declares workflow_dispatch but the job-level and step-level conditionals reference github.event.issue and github.event.comment.body (in the dispatch job's if condition), which exist only for issue_comment events; add the missing issue_comment trigger so those fields are present (e.g., include issue_comment under the workflow's on: triggers) or alternatively refactor the job/step if-conditions to only rely on workflow_dispatch inputs; update the workflow's triggers (and any related conditionals) so jobs that check github.event.issue.pull_request and github.event.comment.body run when invoked via an issue comment or adjust the condition to use workflow_dispatch inputs instead (reference: workflow_dispatch, jobs.dispatch and the if: condition using github.event.issue.pull_request and github.event.comment.body)..github/workflows/changelog-build.yml (1)
28-28:⚠️ Potential issue | 🟠 MajorAdd/Document GPG signing setup for
changelog-bot(required bygit commit -S)The workflow runs
git commit -S -m "chore(changelog): regenerate index", but searches for any GPG/signing/sign.*commitconfiguration in markdown docs and.github/workflows/returned no matches—so there’s no documented setup for thechangelog-botuser (or the token owner). Ensure the workflow (or a called action) imports/configures the GPG key so the signed commit can succeed.Current snippet
git commit -S -m "chore(changelog): regenerate index"🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/changelog-build.yml at line 28, The workflow currently calls git commit -S -m "chore(changelog): regenerate index" but doesn’t provision a GPG key for the changelog-bot/token owner; add steps to import and configure a GPG key and git user signing config before that commit. Specifically, in the workflow that contains the git commit -S invocation add secure retrieval of the bot's private key (from repository or org secrets), a step to import it into gpg (or use actions/setup-gpg or sigstore action), set GPG_TTY if needed, and configure git user.signingkey and user.email/name (or use --author) so git commit -S succeeds; ensure the key is unlocked or configured for non-interactive use and that the secret name is documented for maintainers.
🧹 Nitpick comments (1)
.github/workflows/changelog-build.yml (1)
4-4: ⚡ Quick winVerify the operational impact of removing automatic triggers.
The changelog index will no longer rebuild automatically on pushes to
mainor PRs touchingchangelog/**. Since this workflow now runs only on manual dispatch, the team must remember to trigger it after changelog updates, or the published index may become stale.Consider documenting when/how to manually trigger this workflow (e.g., in
changelog/README.mdor aCONTRIBUTING.mdguide), or add a reminder comment in the PR template for changelog-related changes.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/changelog-build.yml at line 4, The workflow now only exposes workflow_dispatch in changelog-build.yml so the changelog index won’t rebuild automatically; add explicit developer guidance: update the changelog README (or CONTRIBUTING guide) and the PR template to include a short step-by-step note telling reviewers/maintainers how to manually trigger the changelog-build.yml workflow via GitHub Actions (mentioning the workflow_dispatch trigger name and where to find "Run workflow" in the Actions tab), and include a reminder to run it whenever changelog/** files or the index are changed.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@get-started/README.md`:
- Line 7: The deprecation banner in get-started/README.md does not match the
canonical BANNER_BLOCK in scripts/add-deprecation-banner.mjs; update the README
banner text to exactly match the BANNER_BLOCK constant in
scripts/add-deprecation-banner.mjs (or if you intend to change the canonical
text, update BANNER_BLOCK in scripts/add-deprecation-banner.mjs and then
regenerate the docs so all files use the same template), making sure the
wording, links, and punctuation are identical to avoid the automation
overwriting your change.
In `@kite-agent-passport/README.md`:
- Line 7: The README has two conflicting issue-report destinations: the top
deprecation blurb links to "gokite-ai/kite-docs" while another link points to
"gokite-ai/developer-docs/issues/new/choose"; update the secondary link to match
the canonical "https://github.com/gokite-ai/kite-docs" destination (or
vice-versa if you prefer the other repo) so both references point to the same
issue tracker, and make the link text/anchor consistent with the deprecation
notice in the README.
In `@kite-agent-passport/service-provider-guide.md`:
- Line 7: The page currently points issue reports to two different trackers: the
header deprecation notice links to https://github.com/gokite-ai/kite-docs while
the help footer still points to
https://github.com/gokite-ai/developer-docs/issues/new/choose; update the footer
so both references converge on the single canonical tracker (replace the footer
URL/text with the kite-docs link and matching wording from the deprecation
notice) and ensure the footer’s issue-reporting copy matches the header’s
phrasing.
---
Outside diff comments:
In @.github/workflows/changelog-build.yml:
- Line 28: The workflow currently calls git commit -S -m "chore(changelog):
regenerate index" but doesn’t provision a GPG key for the changelog-bot/token
owner; add steps to import and configure a GPG key and git user signing config
before that commit. Specifically, in the workflow that contains the git commit
-S invocation add secure retrieval of the bot's private key (from repository or
org secrets), a step to import it into gpg (or use actions/setup-gpg or sigstore
action), set GPG_TTY if needed, and configure git user.signingkey and
user.email/name (or use --author) so git commit -S succeeds; ensure the key is
unlocked or configured for non-interactive use and that the secret name is
documented for maintainers.
In @.github/workflows/changelog-commands.yml:
- Around line 3-11: The workflow currently only declares workflow_dispatch but
the job-level and step-level conditionals reference github.event.issue and
github.event.comment.body (in the dispatch job's if condition), which exist only
for issue_comment events; add the missing issue_comment trigger so those fields
are present (e.g., include issue_comment under the workflow's on: triggers) or
alternatively refactor the job/step if-conditions to only rely on
workflow_dispatch inputs; update the workflow's triggers (and any related
conditionals) so jobs that check github.event.issue.pull_request and
github.event.comment.body run when invoked via an issue comment or adjust the
condition to use workflow_dispatch inputs instead (reference: workflow_dispatch,
jobs.dispatch and the if: condition using github.event.issue.pull_request and
github.event.comment.body).
---
Nitpick comments:
In @.github/workflows/changelog-build.yml:
- Line 4: The workflow now only exposes workflow_dispatch in changelog-build.yml
so the changelog index won’t rebuild automatically; add explicit developer
guidance: update the changelog README (or CONTRIBUTING guide) and the PR
template to include a short step-by-step note telling reviewers/maintainers how
to manually trigger the changelog-build.yml workflow via GitHub Actions
(mentioning the workflow_dispatch trigger name and where to find "Run workflow"
in the Actions tab), and include a reminder to run it whenever changelog/**
files or the index are changed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 954b14fd-53ca-4ae2-b97f-b06c33b4f27e
📒 Files selected for processing (67)
.github/workflows/changelog-build.yml.github/workflows/changelog-commands.ymlREADME.mdchangelog/2026/2026-05-19-backend-v1-1-0.mdchangelog/2026/2026-05-19-cli-v1-3-4.mdchangelog/2026/2026-05-19-skills-v0-9-1.mdchangelog/2026/2026-05-19-web-v1-2-0.mdchangelog/README.mddev/README.mddocs/STYLING_GUIDE.mdget-started-why-kite/tokenomics.mdget-started/README.mdget-started/architecture-and-design-pillars.mdget-started/core-concepts-and-terminology.mdget-started/introduction-and-mission.mdget-started/key-use-cases-and-players.mdget-started/whitepaper-references.mdintegration-guide/README.mdintegration-guide/api-agent-builder-guide.mdintegration-guide/api-merchants-payment-providers.mdintegration-guide/api-references.mdintegration-guide/case-study-app-store.mdintegration-guide/sdk-api-overview-for-developers/README.mdintegration-guide/sdk-api-overview-for-developers/agent-builder-guide.mdintegration-guide/sdk-api-overview-for-developers/merchant-integration-guide.mdintegration-guide/workflow-agent-builders.mdintegration-guide/workflow-merchants-payment-providers.mdintegration-guide/workflow-overview.mdintegration-guide/workflow-overview/README.mdintegration-guide/workflow-overview/workflow-a-agent-builders.mdintegration-guide/workflow-overview/workflow-b-merchants-and-payment-providers.mdkite-agent-passport/README.mdkite-agent-passport/add-kite-tokens-external-wallet.mdkite-agent-passport/beginner-setup.mdkite-agent-passport/cli-reference.mdkite-agent-passport/funding.mdkite-agent-passport/service-provider-guide.mdkite-chain/1-getting-started/README.mdkite-chain/1-getting-started/faqs.mdkite-chain/1-getting-started/network-information.mdkite-chain/1-getting-started/tools.mdkite-chain/10-layerzero-kite-integration/README.mdkite-chain/11-goldsky-kite-integration/README.mdkite-chain/12-lucid-kite-integration/README.mdkite-chain/2-fundamentals/README.mdkite-chain/2-fundamentals/blockchain-fundamentals.mdkite-chain/2-fundamentals/smart-contract-basics.mdkite-chain/3-developing/README.mdkite-chain/3-developing/counter-smart-contract-hardhat.mdkite-chain/3-developing/counter-smart-contract-remix.mdkite-chain/3-developing/setup-environment.mdkite-chain/3-developing/smart-contracts-list.mdkite-chain/3-developing/voting-smart-contract.mdkite-chain/4-building-dapps/README.mdkite-chain/4-building-dapps/counter-dapp.mdkite-chain/4-building-dapps/token-minter.mdkite-chain/4-building-dapps/voting-dapp.mdkite-chain/5-advanced/README.mdkite-chain/5-advanced/account-abstraction-sdk.mdkite-chain/5-advanced/multisig-wallet.mdkite-chain/6-reference.mdkite-chain/7-kite-node/README.mdkite-chain/7-kite-node/mainnet-network-information.mdkite-chain/7-kite-node/mainnet-node-operations.mdkite-chain/8-kite-stablecoin/stablecoin-gasless-transfer.mdkite-chain/9-gasless-integration/README.mdkite-chain/mica-whitepaper.md
✅ Files skipped from review due to trivial changes (39)
- kite-chain/2-fundamentals/blockchain-fundamentals.md
- kite-chain/7-kite-node/mainnet-network-information.md
- kite-chain/6-reference.md
- kite-chain/2-fundamentals/README.md
- integration-guide/sdk-api-overview-for-developers/README.md
- get-started/whitepaper-references.md
- integration-guide/sdk-api-overview-for-developers/merchant-integration-guide.md
- integration-guide/case-study-app-store.md
- dev/README.md
- kite-chain/1-getting-started/tools.md
- kite-chain/7-kite-node/mainnet-node-operations.md
- integration-guide/workflow-overview/workflow-b-merchants-and-payment-providers.md
- docs/STYLING_GUIDE.md
- kite-chain/12-lucid-kite-integration/README.md
- changelog/2026/2026-05-19-backend-v1-1-0.md
- kite-chain/3-developing/voting-smart-contract.md
- kite-chain/3-developing/README.md
- kite-chain/mica-whitepaper.md
- kite-chain/8-kite-stablecoin/stablecoin-gasless-transfer.md
- kite-chain/7-kite-node/README.md
- kite-agent-passport/cli-reference.md
- kite-agent-passport/add-kite-tokens-external-wallet.md
- integration-guide/workflow-overview/workflow-a-agent-builders.md
- kite-chain/2-fundamentals/smart-contract-basics.md
- changelog/2026/2026-05-19-web-v1-2-0.md
- kite-chain/5-advanced/README.md
- get-started/architecture-and-design-pillars.md
- integration-guide/workflow-merchants-payment-providers.md
- changelog/README.md
- kite-chain/10-layerzero-kite-integration/README.md
- integration-guide/sdk-api-overview-for-developers/agent-builder-guide.md
- kite-chain/3-developing/counter-smart-contract-remix.md
- kite-agent-passport/funding.md
- get-started/core-concepts-and-terminology.md
- integration-guide/api-references.md
- get-started-why-kite/tokenomics.md
- kite-agent-passport/beginner-setup.md
- changelog/2026/2026-05-19-skills-v0-9-1.md
- get-started/introduction-and-mission.md
🚧 Files skipped from review as they are similar to previous changes (13)
- integration-guide/workflow-overview/README.md
- kite-chain/4-building-dapps/counter-dapp.md
- kite-chain/3-developing/counter-smart-contract-hardhat.md
- kite-chain/1-getting-started/faqs.md
- integration-guide/workflow-agent-builders.md
- changelog/2026/2026-05-19-cli-v1-3-4.md
- integration-guide/api-merchants-payment-providers.md
- kite-chain/9-gasless-integration/README.md
- kite-chain/3-developing/smart-contracts-list.md
- integration-guide/workflow-overview.md
- kite-chain/3-developing/setup-environment.md
- README.md
- kite-chain/1-getting-started/network-information.md
springzhang-kite
changed the title
springzh
approved these changes
Jun 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit