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
Fix CI (obsolete lockfile) #431
base: react-1.2.x
Are you sure you want to change the base?
Fix CI (obsolete lockfile) #431
Conversation
|
73d851a
to
78aa455
Compare
@robertknight I've added ci for target branch |
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 should be targetting main
, not the one-off branch (that I'm still not sure we'll support a release for). Everything in the workflow files looks like it should be reverted.
@@ -8,18 +8,17 @@ jobs: | |||
build: | |||
runs-on: ubuntu-latest | |||
steps: | |||
- uses: actions/checkout@v2 |
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.
Following the theme, please don't alter things unless absolutely necessary.
The goal with all PRs is to try to keep the diff concise and targeted -- it makes it so much easier to navigate the blame later on if needs be. Sometimes it can make sense to toss a bunch of changes together, like if you were really altering the CI, but updating actions is not necessary from what I can see nor within the scope of bumping the lock file.
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.
I think CI is needed to ensure that all works fine in the branch, also it's useful to release new version with changesets
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.
We don't use changesets for publishing, and again, that fix should be a one-off. We really don't want to be supporting 1.2.x
beyond 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.
Removed commit
78aa455
to
94b7768
Compare
Updated lockfile to fix CI
Partially based on #391