Skip to content

docs(gov): fix proposer field comment - #534

Open
zloglevel wants to merge 1 commit into
initia-labs:mainfrom
zloglevel:docs/gov-proposer-comment
Open

docs(gov): fix proposer field comment#534
zloglevel wants to merge 1 commit into
initia-labs:mainfrom
zloglevel:docs/gov-proposer-comment

Conversation

@zloglevel

@zloglevel zloglevel commented Aug 29, 2026

Copy link
Copy Markdown

Description

Closes: #XXXX

Correct “proposal sumbitter” to “proposal submitter” in the Proposal.proposer protobuf comment. This improves generated documentation without changing the schema or wire format.


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, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Signed-off-by: zloglevel <loglevel@outlook.com>
@zloglevel
zloglevel requested a review from a team as a code owner August 29, 2026 18:16
@coderabbitai

coderabbitai Bot commented Aug 29, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e7244a9d-852a-403e-b49a-860f75e8380d

📥 Commits

Reviewing files that changed from the base of the PR and between 84dbc22 and 2271e39.

📒 Files selected for processing (1)
  • proto/initia/gov/v1/gov.proto

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.


📝 Walkthrough

Walkthrough

The change corrects a spelling error in the comment above the proposer field in the Proposal message. It does not change the schema or runtime behavior.

Changes

Governance comment correction

Layer / File(s) Summary
Correct proposer comment
proto/initia/gov/v1/gov.proto
The comment changes “sumbitter” to “submitter”.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 2271e

This PR corrects a documentation typo in the proposer field without changing runtime behavior, APIs, or wire format. No actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: tansawit

Poem

A rabbit spotted words askew
One typo hopped away from view
“Submitter” now stands clear
The schema stays unchanged here
Carrots celebrate the cheer

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly and concisely describes the documentation comment correction in the proposer field.
Description check ✅ Passed The description accurately explains the typo correction and states that the schema and wire format remain unchanged.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

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