Skip to content

Commit

Permalink
Merge branch 'main' into julien/autocli-protocolpool
Browse files Browse the repository at this point in the history
  • Loading branch information
julienrbrt committed Oct 2, 2024
2 parents 6dfed36 + bfdd954 commit 50859c3
Show file tree
Hide file tree
Showing 179 changed files with 6,035 additions and 4,499 deletions.
2 changes: 1 addition & 1 deletion CODING_GUIDELINES.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ Make sure your code is well tested:
We expect tests to use `require` or `assert` rather than `t.Skip` or `t.Fail`,
unless there is a reason to do otherwise.
When testing a function under a variety of different inputs, we prefer to use
[table driven tests](https://github.com/golang/go/wiki/TableDrivenTests).
[table driven tests](https://go.dev/wiki/TableDrivenTests).
Table driven test error messages should follow the following format
`<desc>, tc #<index>, i #<index>`.
`<desc>` is an optional short description of what's failing, `tc` is the
Expand Down
6 changes: 3 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -200,7 +200,7 @@ that you would like early feedback and tagging whoever you would like to receive
Codeowners are marked automatically as the reviewers.

All PRs require at least two review approvals before they can be merged (one review might be acceptable in
the case of minor changes to [docs](./.github/PULL_REQUEST_TEMPLATE/docs.md) changes that do not affect production code). Each PR template has a reviewers checklist that must be completed before the PR can be merged. Each reviewer is responsible
the case of minor changes to docs changes that do not affect production code). Each PR template has a reviewers checklist that must be completed before the PR can be merged. Each reviewer is responsible
for all checked items unless they have indicated otherwise by leaving their handle next to specific
items. In addition, use the following review explanations:

Expand Down Expand Up @@ -236,7 +236,7 @@ Within the Cosmos SDK we have two forms of documenting decisions, Request For Co

## Dependencies

We use [Go Modules](https://github.com/golang/go/wiki/Modules) to manage
We use [Go Modules](https://go.dev/wiki/Modules) to manage
dependency versions.

The main branch of every Cosmos repository should just build with `go get`,
Expand Down Expand Up @@ -300,7 +300,7 @@ For example, in vscode your `.vscode/settings.json` should look like:

User-facing repos should adhere to the trunk based development branching model: https://trunkbaseddevelopment.com. User branches should start with a user name, example: `{moniker}/{issue#}-branch-name`.

The Cosmos SDK repository is a [multi Go module](https://github.com/golang/go/wiki/Modules#is-it-possible-to-add-a-module-to-a-multi-module-repository) repository. It means that we have more than one Go module in a single repository.
The Cosmos SDK repository is a [multi Go module](https://go.dev/wiki/Modules#is-it-possible-to-add-a-module-to-a-multi-module-repository) repository. It means that we have more than one Go module in a single repository.

The Cosmos SDK utilizes [semantic versioning](https://semver.org/).

Expand Down
Loading

0 comments on commit 50859c3

Please sign in to comment.