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.

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

ci: give holesky-test workflow access to secrets via pull_request_target #153

Merged

Conversation

samlaf
Copy link
Collaborator

@samlaf samlaf commented Sep 26, 2024

Needed to be able to run the holesky test in #150

@samlaf samlaf requested a review from bxue-l2 September 26, 2024 22:39
@samlaf
Copy link
Collaborator Author

samlaf commented Sep 26, 2024

cc @anupsv

@samlaf samlaf merged commit 15b10fd into main Sep 26, 2024
6 checks passed
@samlaf samlaf deleted the test--switch-holesky-test-workflow-to-use-pull-request-target branch September 26, 2024 22:44
samlaf added a commit that referenced this pull request Oct 30, 2024
…uest_target (#153)"

This reverts commit 15b10fd.
The commit was doing things very wrong. I hadn't understood how pull_request_target works.
Was causing the workflow to run against main branch head commit instead of PR commit.
We will need to find another solution to the problem of letting external contributors run this workflow.
samlaf added a commit that referenced this pull request Oct 31, 2024
* fix(e2e tests): missing new eigenda-client required config fields - ethrpc and svcmanageraddr

* Revert "ci: give holesky-test workflow access to secrets via pull_request_target (#153)"

This reverts commit 15b10fd.
The commit was doing things very wrong. I hadn't understood how pull_request_target works.
Was causing the workflow to run against main branch head commit instead of PR commit.
We will need to find another solution to the problem of letting external contributors run this workflow.

* ide: update vscode settings.json with env vars to run holesky testnet e2e tests

* docs: shorten svcManagerAddr holesky testnet comment

* tests: add panic when both INTEGRATION and TESTNET env vars are set

This forces test runner to be fully aware of which test suite he is running (otherwise it implicitly runs the TESTNET suite)

* style: make handleGetShared returned error print hex encoded commitment

Previously it was printing as byte array, which is unreadable and clutters logs

* docs: better comments in metrics middleware

* deps: upgrade eigenda dep to regression fix commit

TODO: will need to update this after that PR is merged

* deps: update eigenda dependency to master head

Just merged Layr-Labs/eigenda#849 which will fix our ci bug
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