Skip to content

Conversation

@troian
Copy link
Member

@troian troian commented Sep 9, 2025

Description

Closes: #XXXX


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.

I have...

  • included the correct type prefix in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

@troian troian requested a review from a team as a code owner September 9, 2025 10:37
@coderabbitai
Copy link

coderabbitai bot commented Sep 9, 2025

Walkthrough

Updated documentation: fixed a typo in README, consolidated and added a “Roadmap and contributing” section linking to CONTRIBUTING.md, and changed two issue-reporting references in CONTRIBUTING.md to point at the Akash Network support issues repository. No code or API changes.

Changes

Cohort / File(s) Summary of changes
README edits
README.md
Fixed typo ("indept" → "indepth"), added a new top "Roadmap and contributing" section with guidance to open issues in the support repository and a link to CONTRIBUTING.md, removed a duplicate later section, and adjusted spacing/formatting.
CONTRIBUTING links
CONTRIBUTING.md
Updated two documentation references for reporting typos and listing open roadmap issues to point to the Akash Network support issues repository instead of the node issues repository.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks (2 passed, 1 warning)

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The pull request description contains only the default template instructions and placeholders without any specific information about the actual documentation changes made in this PR, making it unrelated to the changeset. Please replace the placeholder content with a summary of the documentation changes, including the added “Roadmap and contributing” section and references to the support repository, and note any related issue numbers.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The title concisely and accurately summarizes the primary change of this pull request, which is updating the README to document the steps for creating an issue in the support repository, and adheres to the conventional commit style with a clear docs prefix.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.

Poem

I twitch my whiskers, paws in sync,
I mend a link, give docs a wink.
Roadmaps polished, duplicates gone,
Contributions pointed to the lawn.
A rabbit's hop — tidy, light, and bright. 🐇✨

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9dce962 and 466c692.

📒 Files selected for processing (2)
  • CONTRIBUTING.md (2 hunks)
  • README.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • CONTRIBUTING.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • README.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: lint
  • GitHub Check: tests
  • GitHub Check: release-dry-run
  • GitHub Check: coverage
  • GitHub Check: build-bins
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch readme

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
README.md (1)

18-25: Polish heading, grammar, and link to support issue chooser

Title case the heading, fix wording, and point to the new-issue chooser. Add a period to the last sentence.

-# Roadmap and contributing
+# Roadmap and Contributing
@@
-Should you with to suggest feature or report an issue please open ticket in [support repo](https://github.com/akash-network/support/issues)
+To suggest a feature or report an issue, please open a ticket in the [support repository](https://github.com/akash-network/support/issues/new/choose).
@@
-Akash is written in Golang and is Apache 2.0 licensed - contributions are welcomed whether that means providing feedback, testing existing and new feature or hacking on the source.
+Akash is written in Go and is Apache 2.0 licensed—contributions are welcome, whether that means providing feedback, testing existing and new features, or hacking on the source.
@@
-To become a contributor, please see the guide on [contributing](CONTRIBUTING.md)
+To become a contributor, please see the guide on [contributing](CONTRIBUTING.md).
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 590dcd1 and 9dce962.

📒 Files selected for processing (2)
  • CONTRIBUTING.md (1 hunks)
  • README.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: sims
  • GitHub Check: release-dry-run
  • GitHub Check: lint
  • GitHub Check: coverage
  • GitHub Check: tests
  • GitHub Check: build-bins

#### I've found a typo

* A Pull Request is not necessary. Raise an [Issue](https://github.com/akash-network/node/issues) and we'll fix it as soon as we can.
* A Pull Request is not necessary. Raise an [Issue](https://github.com/akash-network/support/issues) and we'll fix it as soon as we can.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Deep-link to “New issue” chooser in support repo

Linking to the issues list increases a click; point directly to the new-issue chooser.

-* A Pull Request is not necessary. Raise an [Issue](https://github.com/akash-network/support/issues) and we'll fix it as soon as we can.
+* A Pull Request is not necessary. Raise an [issue](https://github.com/akash-network/support/issues/new/choose) and we'll fix it as soon as we can.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
* A Pull Request is not necessary. Raise an [Issue](https://github.com/akash-network/support/issues) and we'll fix it as soon as we can.
* A Pull Request is not necessary. Raise an [issue](https://github.com/akash-network/support/issues/new/choose) and we'll fix it as soon as we can.
🤖 Prompt for AI Agents
In CONTRIBUTING.md around line 31, the current link points to the issues list;
update it to deep-link directly to the new-issue chooser by replacing the URL
https://github.com/akash-network/support/issues with
https://github.com/akash-network/support/issues/new so clicking goes straight to
the "New issue" form.

found in the [design documentation](https://docs.akash.network); and the target workload definition spec is [here](https://docs.akash.network/sdl).

For an indept understanding of the code [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/akash-network/node)
For an indepth understanding of the code [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/akash-network/node)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix typo: “indepth” → “in-depth”

-For an indepth understanding of the code [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/akash-network/node)
+For an in-depth understanding of the code [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/akash-network/node)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
For an indepth understanding of the code [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/akash-network/node)
For an in-depth understanding of the code [![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/akash-network/node)
🤖 Prompt for AI Agents
In README.md around line 16, the word "indepth" is misspelled; replace it with
the hyphenated form "in-depth" so the sentence reads "For an in-depth
understanding of the code ..." and keep the rest of the line (the badge link)
unchanged.

@troian troian merged commit 8dcc9fc into main Sep 9, 2025
14 of 17 checks passed
@troian troian deleted the readme branch September 9, 2025 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants