Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Dockerfile and workflow to add ibc-go version as label upon release #3063

Merged
merged 5 commits into from
Jan 26, 2023
Merged

Update Dockerfile and workflow to add ibc-go version as label upon release #3063

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
b89a92f
chore: update Dockerfile and workflow to add ibc-go version as label
chatton Jan 26, 2023
9e13f2c
chore: remove e2e directory and add docker build task
chatton Jan 26, 2023
6408d6b
chore: remove e2e workflows from v7.0.0
chatton Jan 26, 2023
9f8a888
chore: remove build e2e workflow
chatton Jan 26, 2023
fb63240
chore: removing links to e2e markdown files
chatton Jan 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
chore: removing links to e2e markdown files
  • Loading branch information
@chatton
chatton committed Jan 26, 2023
commit fb63240c089cf796c4768aa6f6e9e7ecdcb51274
2 changes: 1 addition & 1 deletion MAINTAINERSHIP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Once the spec has been given initial approval, `ibc-go` engineering will coordin

The code that is presented should adhere to our [code contributor guidelines](https://github.com/cosmos/ibc-go/blob/main/CONTRIBUTING.md).

More details on what code walkthrough should cover will be provided by the `ibc-go` engineering team on a case by case basis. However, the code should be sufficiently unit and [E2E tested](https://github.com/cosmos/ibc-go/blob/main/e2e/README.md). Think about preparing for this process similarly to submitting a codebase for audit :)
More details on what code walkthrough should cover will be provided by the `ibc-go` engineering team on a case by case basis. However, the code should be sufficiently unit and E2E tested. Think about preparing for this process similarly to submitting a codebase for audit :)

Please indicate the expected contribution of your team maintainership, if any. This contribution should also include ideas about devrels support and support for product on social media.

Expand Down
4 changes: 0 additions & 4 deletions docs/dev/project-structure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,3 @@ This folder contains all the Protobuf files used for
## `testing`

This package contains the implementation of the testing package used in unit and integration tests. Please read the [package's documentation](../../testing/README.md) for more information.

## `e2e`

This folder contains all the e2e tests of ibc-go. Please read the [module's documentation](../../e2e/README.md) for more information.