-
Notifications
You must be signed in to change notification settings - Fork 26
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
#186 Add input completion status #198
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
env: | ||
E2E_BASE_URL: ${{ github.event.deployment_status.environment_url }} | ||
|
||
- name: Update check status to the outcome |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, @brunomenezes , I regards to the failing e2e tests, I was expecting the build to fail with the related e2e job as well, but that was not the case. It was passing ok although the e2e job that we run on sepolia preview url was failing.
Because of this I had to implement this step. It will run the reportGitHubStatusCheck
script, which will then post an e2e status to the build - "End-to-end (Preview – rollups-explorer-sepolia)". That status can be either success
or failure
so in the case of the latter the build will fail as well.
I added the input completion status and also covered the new logic with unit tests.