Skip to content

Conversation

@phessophissy
Copy link

@phessophissy phessophissy commented Jan 24, 2026

Summary

This PR adds standard open source community files and updates documentation to improve the contributor experience.

Changes

File Change
CONTRIBUTING.md New - Contribution guidelines with setup instructions, coding standards, and PR process
CODE_OF_CONDUCT.md New - Contributor Covenant Code of Conduct v2.0
NOTICE.md Fixed - Updated copyright year from 2022 to 2025 (now matches README)
README.md Updated - Added Contributing section with links to new community files

Why This Matters

  • Better contributor experience — New contributors now have clear guidelines on how to contribute
  • Community standards — Code of Conduct establishes expectations for community behavior
  • Consistency — Copyright year now matches across NOTICE.md and README.md
  • Discoverability — GitHub will automatically recognize and display these community health files

Details

CONTRIBUTING.md includes:

  • Prerequisites (Go 1.21+)
  • Development setup instructions
  • How to run tests (make tests) and linter (make lint)
  • Commit message conventions
  • Pull request guidelines

CODE_OF_CONDUCT.md

  • Based on Contributor Covenant v2.0
  • Industry-standard code of conduct used by many open source projects

Summary by CodeRabbit

  • Documentation
    • Added Code of Conduct establishing community standards and behavioral expectations for contributors
    • Added Contributing Guidelines with development setup, testing procedures, and submission workflow
    • Enhanced README with links to contribution resources and community guidelines
    • Updated copyright information to 2025

✏️ Tip: You can customize this high-level summary in your review settings.

- Add CONTRIBUTING.md with contribution guidelines
- Add CODE_OF_CONDUCT.md (Contributor Covenant)
- Update NOTICE.md copyright year (2022 → 2025) to match README
- Add Contributing section to README with links to new files
@coderabbitai
Copy link

coderabbitai bot commented Jan 24, 2026

📝 Walkthrough

Walkthrough

This PR adds governance and contribution documentation to the repository. A new Code of Conduct document following the Contributor Covenant v2.0 is introduced, along with comprehensive Contributing guidelines for the Injective Protocol Go SDK. Project notices and README are updated to reflect these additions.

Changes

Cohort / File(s) Summary
Governance & Contribution Documentation
CODE_OF_CONDUCT.md, CONTRIBUTING.md
Added new Code of Conduct following Contributor Covenant v2.0 with enforcement responsibilities and reporting channels. Created comprehensive Contributing guidelines covering setup, development process, commit messages, coding standards, and pull request procedures for the Injective Protocol Go SDK.
Metadata & README Updates
NOTICE.md, README.md
Updated copyright year in NOTICE.md from 2020-2022 to 2020-2025. Added Contributing section to README.md with links to new governance documents.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰✨ New guidelines hop into place,
A Code of Conduct sets the pace,
Contributors welcome, treated fair,
With kindness woven everywhere! 🌟

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add community files and improve documentation' clearly and accurately summarizes the main changes: addition of community files (CODE_OF_CONDUCT.md, CONTRIBUTING.md) and documentation improvements (README.md update).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

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

🤖 Fix all issues with AI agents
In `@CONTRIBUTING.md`:
- Around line 74-77: The CONTRIBUTING.md currently instructs contributors to
create a branch from `dev` using the example `git checkout -b
feature/your-feature-name`; update that instruction to use the repo's actual
base branch (replace `dev` with `master` or the correct default branch name) and
adjust the example branch command and any surrounding text to consistently
reference `master` (or the correct default) so contributors are directed to the
proper base branch.
- Around line 35-36: Update the Go prerequisite in CONTRIBUTING.md: replace the
string "Go 1.21 or later" with "Go 1.23 or later" so it matches the go directive
in go.mod (which currently reads "go 1.23.9"); leave other entries (e.g.,
"Make") unchanged.

Comment on lines +35 to +36
- Go 1.21 or later
- Make
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

cat go.mod | grep -E '^go\s+'

Repository: InjectiveLabs/sdk-go

Length of output: 73


Update Go version requirement to match go.mod.

The CONTRIBUTING.md states "Go 1.21 or later," but go.mod declares go 1.23.9. Update the prerequisite to "Go 1.23 or later" for accuracy.

🤖 Prompt for AI Agents
In `@CONTRIBUTING.md` around lines 35 - 36, Update the Go prerequisite in
CONTRIBUTING.md: replace the string "Go 1.21 or later" with "Go 1.23 or later"
so it matches the go directive in go.mod (which currently reads "go 1.23.9");
leave other entries (e.g., "Make") unchanged.

Comment on lines +74 to +77
1. Create a new branch from `dev`:
```bash
git checkout -b feature/your-feature-name
```
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Branch base likely incorrect.

The guide says to branch from dev, but this repo appears to target master. This will misdirect contributors.

✅ Suggested fix
-1. Create a new branch from `dev`:
+1. Create a new branch from `master`:
📝 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
1. Create a new branch from `dev`:
```bash
git checkout -b feature/your-feature-name
```
1. Create a new branch from `master`:
🤖 Prompt for AI Agents
In `@CONTRIBUTING.md` around lines 74 - 77, The CONTRIBUTING.md currently
instructs contributors to create a branch from `dev` using the example `git
checkout -b feature/your-feature-name`; update that instruction to use the
repo's actual base branch (replace `dev` with `master` or the correct default
branch name) and adjust the example branch command and any surrounding text to
consistently reference `master` (or the correct default) so contributors are
directed to the proper base branch.

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.

1 participant