Fix : errors and broken links

[nnsW3]

Hello
I fixed some spelling errors and broken links.
Glad I could help.
Br, Elias.

Summary by CodeRabbit

• Documentation

  • Updated bug reporting URL in Release Notes template
  • Minor grammatical corrections in IBC hooks README

• Bug Fixes

  • Corrected typo in Darwin AMD64 build workflow step name
  • Fixed variable name typo in indexer reader method

• New Features

  • Added new query methods for EVM-related operations in minievm package, including contract code retrieval, state querying, and contract call execution

[coderabbitai]

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 golangci-lint (1.62.2)

level=warning msg="[runner] Can't run linter goanalysis_metalinter: buildir: failed to load package injective: could not load export data: no export data for "github.com/cosmos/relayer/v2/relayer/codecs/injective""
level=error msg="Running error: can't run linter goanalysis_metalinter\nbuildir: failed to load package injective: could not load export data: no export data for "github.com/cosmos/relayer/v2/relayer/codecs/injective""

Walkthrough

This pull request encompasses several minor modifications across different files in the Initia project. The changes include updating a bug reporting URL in the Release Notes template, correcting a typo in a Darwin build workflow, adding new query methods to the EVM API, making grammatical improvements in IBC hooks documentation, and fixing a variable name in the indexer reader. These updates appear to be focused on improving documentation, build processes, and code clarity.

Changes

File	Change Summary
.github/ISSUE_TEMPLATE/Release_notes.md	Updated bug reporting URL from initia-labs/initia-labs to initia-labs/initia
.github/workflows/build-darwin-amd64.yml	Corrected step name from "Darwin ADM642" to "Darwin AMD642"
api/minievm/evm/v1/query.pulsar.go	Added new query methods for EVM contract interactions, including Code, State, ERC20Factory, ERC20Wrapper, ContractAddrByDenom, Denom, Call, and Params
app/ibc-hooks/README.md	Made minor grammatical corrections, such as fixing "cryptogaphically" to "cryptographically"
indexer/reader.go	Renamed variable txRecept to txReceipt in IterateBlockTxReceipts method

Sequence Diagram

sequenceDiagram
    participant User
    participant EVMQuery
    participant ContractRegistry
    participant EVMRuntime

    User->>EVMQuery: Request Contract Details
    EVMQuery->>ContractRegistry: Retrieve Contract Address
    ContractRegistry-->>EVMQuery: Return Contract Address
    EVMQuery->>EVMRuntime: Execute Query (Code/State/Call)
    EVMRuntime-->>EVMQuery: Return Query Results
    EVMQuery-->>User: Provide Contract Information

Loading

Possibly related PRs

• feat: track latest 256 cosmos block hashes #76: Transaction handling method modifications in indexer/abci.go
• fix: tx pool endpoint to return queued txs and apply mempool wrapper #77: Enhancements to MinitiaApp structure in app/app.go
• fix: return tx indexing error if tx in pending or queued status  #88: Transaction pool endpoint modifications

Poem

🐰 In the realm of code, a rabbit's delight,
URLs fixed, workflows set just right,
Queries dance, docs shine so clear,
Bugs retreat in coding's frontier,
Initia's path, now smooth and bright! 🚀

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 703e4d7 and 5757d84.

📒 Files selected for processing (5)

• .github/ISSUE_TEMPLATE/Release_notes.md (2 hunks)
• .github/workflows/build-darwin-amd64.yml (1 hunks)
• api/minievm/evm/v1/query.pulsar.go (1 hunks)
• app/ibc-hooks/README.md (3 hunks)
• indexer/reader.go (1 hunks)

✅ Files skipped from review due to trivial changes (3)

• app/ibc-hooks/README.md
• .github/workflows/build-darwin-amd64.yml
• .github/ISSUE_TEMPLATE/Release_notes.md

🔇 Additional comments (1)

indexer/reader.go (1)

68-68: LGTM! Variable name correction improves readability.

The variable name change from txRecept to txReceipt enhances code clarity and maintains consistency with the function name TxReceiptByHash.

Also applies to: 73-73