Skip to content

Conversation

@cloud-j-luna
Copy link
Member

@cloud-j-luna cloud-j-luna commented Jun 30, 2025

🌟 PR Title

chore: create CONTRIBUTING.md

📝 Description

Introduce CONTRIBUTING.md to the akash-api repository.

🔧 Purpose of the Change

  • New feature implementation
  • Bug fix
  • Documentation update
  • Code refactoring
  • Dependency upgrade
  • Other: [specify]

✅ Checklist

  • I've updated relevant documentation
  • Code follows Akash Network's style guide
  • I've added/updated relevant unit tests
  • Dependencies have been properly updated
  • I agree and adhered to the Contribution Guidelines

📎 Notes for Reviewers

[Include any additional context, architectural decisions, or specific areas to focus on]

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive CONTRIBUTING.md file with detailed guidelines on contributing, development setup, coding standards, testing, PR submission, release management, and community support for the repository.

@cloud-j-luna cloud-j-luna requested a review from a team as a code owner June 30, 2025 21:11
@coderabbitai
Copy link

coderabbitai bot commented Jun 30, 2025

Walkthrough

A new CONTRIBUTING.md file has been introduced to the repository. This document details contribution guidelines, including environment setup, development practices, PR requirements, testing, release process, and community engagement, all tailored to the akash-api repository and aligned with Akash Network standards.

Changes

File(s) Change Summary
CONTRIBUTING.md Added comprehensive contribution guidelines, including setup, development, PR process, testing, release, and community support.

Suggested labels

Type: CI

Suggested reviewers

  • troian

Poem

A new guide has hopped into view,
With steps for all contributors, old and new.
From setup to testing, it’s clear and bright,
Ensuring our code is always right.
So follow the path, and join the fun—
With every commit, we all become one!
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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: 1

🧹 Nitpick comments (5)
CONTRIBUTING.md (5)

37-41: Standardise bullet list marker (- instead of *)

Lines 38-40 mix * with earlier -, triggering MD004 and making the list style inconsistent. Use a single marker throughout the doc:

-* Report issues at the Akash support repo, tagged with repo/akash-api.
-* All PRs must reference an open issue in the support repo. 
-* Label issues suitable for new contributors as good first issue or ready-for-community-dev.
+- Report issues in the Akash support repo, tagged `repo/akash-api`.
+- All PRs must reference an open issue in the support repo. 
+- Label issues suitable for new contributors as **good first issue** or **ready-for-community-dev**.

46-55: Fix mixed bullet style & improve Go-centric wording

Same MD004 problem plus a minor clarity tweak (“don’t ignore them” ➜ “do not ignore them”):

-* Use `go fmt` on all Go code. 
-* Maintain idiomatic Go naming conventions (CamelCase, explicit error checks).
-* Adhere to the principles of clean code.
+- Use `go fmt ./...` on all Go code.  
+- Maintain idiomatic Go naming conventions (CamelCase, explicit error checks).  
+- Adhere to clean-code principles.
@@
-* Handle errors explicitly, don’t ignore them.
-* Document exported types/functions with GoDoc comments.
-* Document complex unexported functions.
+- Handle errors explicitly; **do not ignore them**.  
+- Document exported types/functions with GoDoc comments.  
+- Document complex unexported functions.

57-63: Add language tag & remove tab indentation for proto-generation block

-* After editing .proto, run:
-	```
-	make proto-gen
-	```
+* After editing `.proto` files, run:
+    ```bash
+    make proto-gen
+    ```

This clears MD010/MD040 and keeps indentation consistent.


74-79: Final lint tidy-up for Testing & CI list

Consistent dash bullets and small copy edit (“must” ➜ “should” for softer tone):

-* Tests should cover your changes—place them in `_test.go` files.
-* All CI checks (format, lint, proto-gen, tests) must pass before merging.
-* The CI pipeline runs workflows on pushes and PRs using GitHub Actions.
+- Tests should cover your changes and live in `_test.go` files.  
+- All CI checks (format, lint, proto-gen, tests) must pass before merging.  
+- The CI pipeline runs GitHub Actions workflows on pushes and pull requests.

90-100: Optional: make the LICENSE link absolute

To avoid broken links when the markdown is viewed outside GitHub (e.g., package registries), consider an absolute link:

-By contributing, you agree that your contributions will be licensed under the project's [Apache 2.0 License](LICENSE).
+By contributing, you agree that your work is licensed under the project’s [Apache 2.0 License](https://github.com/akash-network/akash-api/blob/main/LICENSE).
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 95868d8 and 159ddea.

📒 Files selected for processing (1)
  • CONTRIBUTING.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
CONTRIBUTING.md

22-22: Hard tabs
Column: 4

(MD010, no-hard-tabs)


23-23: Hard tabs
Column: 4

(MD010, no-hard-tabs)


24-24: Hard tabs
Column: 4

(MD010, no-hard-tabs)


25-25: Hard tabs
Column: 1

(MD010, no-hard-tabs)


28-28: Hard tabs
Column: 1

(MD010, no-hard-tabs)


28-28: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


29-29: Hard tabs
Column: 1

(MD010, no-hard-tabs)


30-30: Hard tabs
Column: 1

(MD010, no-hard-tabs)


32-32: Hard tabs
Column: 1

(MD010, no-hard-tabs)


32-32: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


33-33: Hard tabs
Column: 1

(MD010, no-hard-tabs)


34-34: Hard tabs
Column: 1

(MD010, no-hard-tabs)


38-38: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


39-39: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


40-40: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


47-47: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


48-48: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


49-49: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


52-52: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


53-53: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


54-54: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


57-57: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


58-58: Hard tabs
Column: 1

(MD010, no-hard-tabs)


58-58: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


59-59: Hard tabs
Column: 1

(MD010, no-hard-tabs)


60-60: Hard tabs
Column: 1

(MD010, no-hard-tabs)


61-61: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


65-65: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


69-69: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


76-76: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


77-77: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


78-78: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


84-84: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: test
  • GitHub Check: coverage
  • GitHub Check: go

CONTRIBUTING.md Outdated
- **Go** ≥ 1.21
- **GNU Make** ≥ 4.0
- **Bash** ≥ 4.0
- **Protocol Buffer tools** (e.g., `buf`, `protoc`)
Copy link
Member

Choose a reason for hiding this comment

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

no need for this. proto tools are being installed into local cache.
instead direnv is required.

Copy link
Member

Choose a reason for hiding this comment

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

lets also add OS specific installation instructions with all tools listed

Copy link
Member Author

Choose a reason for hiding this comment

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

Does it make sense for OS specific installations on Akash API? I'm currently on MacOS and don't recall having issues with the installation on Linux as well?

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: 0

♻️ Duplicate comments (1)
CONTRIBUTING.md (1)

61-63: Same tab / language issue in the proto-gen reminder

-	```
-	make proto-gen
-	```
+    ```bash
+    make proto-gen
+    ```
🧹 Nitpick comments (2)
CONTRIBUTING.md (2)

25-30: Use correct branding (“macOS”) and add Linux instructions for parity

MacOS should be spelled macOS per Apple’s branding guidelines.
While you provide Homebrew steps, there’s no equivalent for mainstream Linux distros, leaving most contributors guessing.

-    - **MacOS**
-    ```shell
-    brew install direnv
-    ```
+    - **macOS**
+      ```bash
+      brew install direnv
+      ```
+    - **Ubuntu / Debian**
+      ```bash
+      sudo apt-get update && sudo apt-get install direnv
+      ```

35-37: Remove hard-tabs & specify language to silence markdownlint (MD010, MD040)

Tabs are still present and the fenced block lacks a language identifier:

-	```
-	make proto-gen
-	```
+    ```bash
+    make proto-gen
+    ```
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 159ddea and 3f4215a.

📒 Files selected for processing (1)
  • CONTRIBUTING.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CONTRIBUTING.md

[grammar] ~26-~26: The operating system from Apple is written “macOS”.
Context: ...ps://direnv.net/docs/hook.html) - MacOS ```shell brew install direnv ...

(MAC_OS)

🪛 markdownlint-cli2 (0.17.2)
CONTRIBUTING.md

35-35: Hard tabs
Column: 1

(MD010, no-hard-tabs)


35-35: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


36-36: Hard tabs
Column: 1

(MD010, no-hard-tabs)


37-37: Hard tabs
Column: 1

(MD010, no-hard-tabs)


41-41: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


42-42: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


43-43: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


50-50: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


51-51: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


52-52: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


55-55: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


56-56: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


57-57: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


60-60: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


61-61: Hard tabs
Column: 1

(MD010, no-hard-tabs)


61-61: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


62-62: Hard tabs
Column: 1

(MD010, no-hard-tabs)


63-63: Hard tabs
Column: 1

(MD010, no-hard-tabs)


64-64: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


68-68: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


72-72: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


79-79: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


80-80: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


81-81: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


87-87: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: coverage
  • GitHub Check: test
  • GitHub Check: go
🔇 Additional comments (1)
CONTRIBUTING.md (1)

13-16: Verify Go 1.24 requirement

Go 1.24 has not been released yet; requiring it may unnecessarily block contributors.
Consider “Go ≥ 1.22 (latest stable)” or similar, or clarify why 1.24 is mandatory.

@cloud-j-luna cloud-j-luna requested a review from troian July 2, 2025 20:09
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: 0

♻️ Duplicate comments (2)
CONTRIBUTING.md (2)

35-37: Remove hard-tabs & add bash language tag to fix markdownlint MD010/MD040

The block still contains a tab byte and has no language, so markdownlint will fail CI the same way as the earlier snippet that was already flagged.

-	```
-	make proto-gen
-	```
+    ```bash
+    make proto-gen
+    ```

61-63: Same issue: hard-tabs + missing language in the second proto-gen snippet

-	```
-	make proto-gen
-	```
+    ```bash
+    make proto-gen
+    ```
🧹 Nitpick comments (2)
CONTRIBUTING.md (2)

26-27: Use correct branding – “macOS”, not “MacOS”.

Apple’s OS is stylised as “macOS”.
Update the heading to avoid a spelling nit picked up by LanguageTool.


41-44: Unify list markers for readability & MD004 compliance

The rest of the document uses “-” list markers; switch these three “*” items to dashes to keep a consistent style and silence markdownlint MD004.

-* Report issues at the Akash support repo, tagged with repo/akash-api.
-* All PRs must reference an open issue in the support repo. 
-* Label issues suitable for new contributors as good first issue or ready-for-community-dev.
+- Report issues at the Akash support repo, tagged with repo/akash-api.
+- All PRs must reference an open issue in the support repo. 
+- Label issues suitable for new contributors as good first issue or ready-for-community-dev.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3f4215a and 447280d.

📒 Files selected for processing (1)
  • CONTRIBUTING.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CONTRIBUTING.md

[grammar] ~26-~26: The operating system from Apple is written “macOS”.
Context: ...ps://direnv.net/docs/hook.html) - MacOS ```shell brew install go git ...

(MAC_OS)

🪛 markdownlint-cli2 (0.17.2)
CONTRIBUTING.md

35-35: Hard tabs
Column: 1

(MD010, no-hard-tabs)


35-35: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


36-36: Hard tabs
Column: 1

(MD010, no-hard-tabs)


37-37: Hard tabs
Column: 1

(MD010, no-hard-tabs)


41-41: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


42-42: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


43-43: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


50-50: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


51-51: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


52-52: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


55-55: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


56-56: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


57-57: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


60-60: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


61-61: Hard tabs
Column: 1

(MD010, no-hard-tabs)


61-61: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


62-62: Hard tabs
Column: 1

(MD010, no-hard-tabs)


63-63: Hard tabs
Column: 1

(MD010, no-hard-tabs)


64-64: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


68-68: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


72-72: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


79-79: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


80-80: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


81-81: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)


87-87: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: test
  • GitHub Check: coverage
  • GitHub Check: proto
  • GitHub Check: go

@cloud-j-luna cloud-j-luna requested a review from troian July 3, 2025 20:56
@cloud-j-luna cloud-j-luna self-assigned this Jul 7, 2025
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.

3 participants