-
Notifications
You must be signed in to change notification settings - Fork 11
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
Adding rush change -v
to ci.yml
#95
Conversation
Apparently this is not that simple, I'll have to get back to this later. |
ended being due to the shallow fetch GH actions do by default. It wasn't getting enough of the history on the main branch in order to do the comparison for a rush change. Specifying Added Node 14 while I was at it. I saw @ben-polinsky's other PR to swap out node-sass so we can move up to Node 18+ so didn't bother trying. |
Ensure we are requesting rush changes to be filed.
Resolves #94