-
Notifications
You must be signed in to change notification settings - Fork 77
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!: always resolve SHA against provided main branch #64
Conversation
0577f5e
to
e3eb1d0
Compare
fetch-depth: 0 | ||
|
||
- name: Derive appropriate SHAs for base and head for `nx affected` commands | ||
uses: nrwl/nx-set-shas@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.
Can we reference the action locally instead of by version number here?
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.
Oh, yes, we should
README.md
Outdated
@@ -128,6 +128,7 @@ On a CI system that runs on submitted PRs, we determine what commits to include | |||
|
|||
But what if we want to set up a continuous deployment system | |||
that, as changes get pushed to `master`, builds and deploys | |||
only the affected projects? |
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.
What's up with the newlines within this paragraph? :)
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.
That got lost on another commit. I have fixed it on main and rebased to this PR
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.
LGTM!
Includes first set of tests.
Includes #52 necessary for checks on push.
This results in unfortunate breaking changes for some folks (#57 (comment))
The test set should be expanded later to ensure we check different scenarios.
This is to be investigated as it might need to include a controlled git sub repo.
Related to #62
BREAKING CHANGE