-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
ci(NODE-5652): move vars to expansions #3877
Conversation
c88c09e
to
6ff084b
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.
one optional comment
|
||
const TASKS = []; | ||
const SINGLETON_TASKS = []; | ||
|
||
/** Accepts {key: value} -> returns {key, value}[] */ | ||
function updateExpansions(expansions) { |
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.
jsdoc here maybe?
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.
added
Description
What is changing?
vars
to expansionsadd_expansions_to_env: true
Note to reviewer it is easier to follow changes per commit to skip over misc formatting fixes
Is there new documentation needed for these changes?
No
What is the motivation for this change?
Avoiding use of var removes the risk of breakages when evergreen removes the behavior where vars persist across functions
Double check the following
npm run check:lint
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript