Skip to content

Conversation

jmank88
Copy link
Collaborator

@jmank88 jmank88 commented Aug 16, 2025

Comment on lines 35 to 57
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b # v4.1.4

- name: Set up Go
uses: actions/setup-go@v5
with:
cache-dependency-path: go.sum
go-version-file: go.mod

- name: Ensure modules are tidy
run: |
go install github.com/jmank88/[email protected]
gomods tidy
git add --all
git diff --minimal --cached --exit-code
- name: Ensure mockery has been run
run: |
grep -rl "^// Code generated by mockery" | grep .go$ | xargs -r rm
find . -type f -name .mockery.yaml -execdir mockery \;
git add --all
git diff --stat --cached --exit-code

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
- name: Ensure mockery has been run
run: |
grep -rl "^// Code generated by mockery" | grep .go$ | xargs -r rm
find . -type f -name .mockery.yaml -execdir mockery \;
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mockery is not installed, but nix appears to be using go-mockery. How can we leverage that for this check?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archseer what about this repo? nix does not appear to be used by any CI currently. Is there a way to ensure that I have the same version installed if I just invoke it directly?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archseer bump


- name: Run tests
run: cd relayer && go test -v -count=1 -p=1 -tags=integration ./...
run: cd relayer && go test -count=1 -tags=integration ./...
Copy link
Collaborator Author

@jmank88 jmank88 Sep 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-p=1 slows things down to a single package at a time, and -v adds all the noise of the successful tests to the logstream, crowding out the failed test logs.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Restored -p=1 since we depend on that currently. Why are we limiting ourselves this way?

@jmank88 jmank88 marked this pull request as ready for review September 13, 2025 14:39
@jmank88 jmank88 requested a review from a team as a code owner September 13, 2025 14:39
@jmank88 jmank88 requested a review from archseer September 15, 2025 11:18
@jmank88 jmank88 merged commit 9bff00f into develop Sep 15, 2025
17 of 21 checks passed
@jmank88 jmank88 deleted the tidy branch September 15, 2025 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants