-
Notifications
You must be signed in to change notification settings - Fork 72
BOM-2988: Replace Travis with GitHub CI #245
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
BOM-2988: Replace Travis with GitHub CI #245
Conversation
8528e84
to
d440b8d
Compare
This changes the release trigger from commits to tags. @davidjoy is that in line with fedx practice? |
@nedbat I'm not sure I follow the commits/tags comment... My understanding is that |
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.
Think I'm seeing some issues here w/r/t npm
-> npx
and a storybook action.
I''l note that in frontend-build we already have a Github release workflow. I'd suggest we keep this one consistent with that: https://github.com/edx/frontend-build/blob/master/.github/workflows/release.yml
@davidjoy the
so semantic-release was run after every test run. The new action has:
so the Release CI action is only run when a new tag is pushed, and it's the Release CI that runs semantic-release. |
Oh, thank you, I didn't catch that. That sounds like a sane change; I don't know why we'd have semantic-release run anytime except when merging into master. |
OK, except this is less frequently than that: only when someone explicitly makes and pushes a tag. |
Okay, now I'm confused again... semantic-release is responsible for creating the tags and does that as part of its work, after it figures out the version bump based on the commits being merged in to master. We definitely don't want that to become a manual process, and I'm pretty sure semantic-release will fail if the tag already exists. |
d440b8d
to
c2c6970
Compare
Codecov Report
@@ Coverage Diff @@
## master #245 +/- ##
=======================================
Coverage 80.79% 80.79%
=======================================
Files 38 38
Lines 885 885
Branches 163 163
=======================================
Hits 715 715
Misses 159 159
Partials 11 11 Continue to review full report at Codecov.
|
@davidjoy I've updated the |
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.
Think we're missing the Github Pages deploy. Otherwise the release trigger sounds right.
uses: JamesIves/github-pages-deploy-action@4.1.5 | ||
with: | ||
branch: gh-pages # The branch the action should deploy to. | ||
folder: dist # The folder the action should deploy. |
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.
@davidjoy I'm not sure about the folder
argument. Is the default dict
value okay?
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.
Yes, I think that should be correct (dist
, not dict
, of course, but the code is right!)
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.
Lets get this in there and see if it works!
Issue: BOM-2988
Description
Travis
withGitHub CI
.