iotaledger / iota-rust-sdk

39%

LAST BUILD ON BRANCH develop

branch: develop

CHANGE BRANCH

x

Reset

Sync Branches

• develop
• bindings/full-examples
• chore/filter-bindings-ci-prs
• chore/fix-broken-links
• chore/go-remove-gcc-x86-64-linux-gnu
• chore/pub-mod-types-crate
• chore/rename-go-sdk
• chore/standardize-go-usage
• ci/kotlin-release
• ci/nightly-feature-compat-check
• ci/python-release
• ci/python-release-trigger
• ci/run-ci-marker
• copilot/add-go-readme-file
• feat/async-signing
• feat/bindings-release-trigger
• feat/bindings-release-trigger-go
• feat/ci-coverage
• feat/ci-coverage-2
• feat/ci-run-examples
• feat/go-release
• feat/go-release-bis
• feat/kotlin-changelog
• feat/kotlin-release-trigger
• feat/mnemonic-generation
• feat/move-auth
• feat/move-shared-crypto
• feat/uniffi-export-derived-traits
• fix/ci-package-root
• fix/failingci
• fix/feature-flags
• fix/gen-changelog-nits
• fix/go-release-nits
• fix/head-refs
• fix/iotaTotalSupply-type
• fix/regex-test
• fix/release-pr-title
• fix/txn-builder-dep
• release/iota-go-sdk/0.0.1-alpha.1
• release/iota-sdk-graphql-client/0.0.1-alpha.1
• release/iota-sdk-transaction-builder/0.0.1-alpha.1
• release/iota-sdk/3.0.0-alpha.1

Build # 26136255548

Build Type

push

github

Committed by web-flow

Commit Message

chore: update gRPC client example and add PR guidelines (#1156)

* docs: update gRPC client usage and add PR-size guidance to AGENTS.md

Reflect the new `new_mainnet`/`new_testnet`/`new_devnet`/`new_localnet`
constructors on the gRPC `Client` (PR #1154), and add development notes
encouraging small, focused PRs split across multiple changes when possible.

* chore: document PR title format requirement in AGENTS.md

Note that PR titles are validated by the `pr_title` workflow and must use
one of the allowed Conventional Commits types (`feat`, `fix`, `refactor`,
`chore`, `upstream`, `release`).

* chore: add note on keeping PR descriptions short

Reviewers shouldn't have to read a wall-of-text summary that restates
the diff line-by-line. Cover the why and the high-level what; the code
shows the rest.

* chore: satisfy dprint markdown formatting

Use `_emphasis_` instead of `*emphasis*` to match the markdown plugin's
preferred italic style.

---------

Co-authored-by: Claude <noreply@anthropic.com>

Coverage Stats

8778 of 22465 relevant lines covered (39.07%)

9396.06 hits per line