You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
our local tests pick up the changes from the modules right away. Howevever, the e2e test depends on the go.mod being correctly tagged with the latest version.
As a result, an engineer has to manually run the following command to update the root go.mod:
go get < module > @< commit hash >
go mod tidy
We need a way to automate this process.
Suggested Design
The end goal of this is the following:
detect if osmoutils, osmomath and x/ibc-hooks modules were updated in a PR
if so, auto-open PR to your branch with global go.mod updated to the deps in your branch
I propose splitting this into the following steps / PRs:
Create a script that when run, does the following:
# detect current branch
go get github.com/osmosis-labs/osmosis/osmomath@< branch hash>
go get github.com/osmosis-labs/osmosis/osmoutils@< branch hash>
go get github.com/osmosis-labs/osmosis/x/ibc-hooks@< branch hash>
go mod tidy
Note that for this to work, the current branch must be pushed to remote.
Create a CI job that detects if any of osmomath, osmoutils, x/ibc-hooks` had any changes.
If so, it runs the script and opens a PR against your branch with the changes from script 1 applied.
Acceptance Criteria
The process of updating go.mod is fully automated
Successfully executes every time when an update to osmomath, ``osmoutilsorx/ibc-hooks` is made
Auto-opens a PR against developer's branch with the go.mod changes
The text was updated successfully, but these errors were encountered:
Background
Currently, when we update one of:
osmoutils
osmomath
x/ibc-hooks
our local tests pick up the changes from the modules right away. Howevever, the e2e test depends on the
go.mod
being correctly tagged with the latest version.As a result, an engineer has to manually run the following command to update the root
go.mod
:We need a way to automate this process.
Suggested Design
The end goal of this is the following:
I propose splitting this into the following steps / PRs:
Note that for this to work, the current branch must be pushed to remote.
osmomath
,osmoutils
, x/ibc-hooks` had any changes.Acceptance Criteria
go.mod
is fully automatedosmomath
, ``osmoutilsor
x/ibc-hooks` is madego.mod
changesThe text was updated successfully, but these errors were encountered: