-
Notifications
You must be signed in to change notification settings - Fork 10
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
Include lint and test jobs for node-ci-push workflow (using reusable workflow) #2348
Conversation
…bled on feature branches (this is so feature branches can be updated with main)
|
|
||
coverage: |
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.
This job can be removed since the Test workflow also gathers coverage!
Size Change: 0 B Total Size: 100 kB ℹ️ View Unchanged
|
A new build was pushed to Chromatic! 🚀https://5e1bf4b385e3fb0020b7073c-lthespwsvf.chromatic.com/ Chromatic results:
|
token: ${{ secrets.CODECOV_TOKEN }} | ||
files: ./coverage/coverage-final.json | ||
uses: ./.github/workflows/node-ci-test.yml | ||
secrets: |
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.
Here, we are able to pass tokens using secrets
GeraldRequired Reviewers
Don't want to be involved in this pull request? Comment |
npm Snapshot: NOT Published🤕 Oh noes!! We couldn't find any changesets in this PR (edb0ac0). As a result, we did not publish an npm snapshot for you. |
68b5dbd
to
89c9872
Compare
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.
This is a great improvement! thanks for the detailed description and iterating on the problem 👏 🚀
Added some notes around these findings here: https://khanacademy.atlassian.net/wiki/x/AYGUyQ |
Summary:
node-ci-push.yml
workflownode-ci-push
andnode-ci-pr
can use the same configSee #2346 for an alternative where we use composite actions instead to share configuration
Update: We decided to use reusable workflows so that the logs are easier to read for the steps and we can use the
secrets
config (which isn't supported by composite actions). The branch rules have been updated to look forLint / Lint
andTest / Test
checks.Pros:
node-ci-push
andnode-ci-pr
Cons:
Node CI (PR) / Lint / Lint
instead of justNode CI (PR) / Lint
) and the github checks will need to be updated (let me know though if there's a way around this!)Issue: WB-1778
Test plan: