-
Notifications
You must be signed in to change notification settings - Fork 30k
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
doc: rename the startup performance initiative to startup snapshot #47111
Conversation
The initiative has been more focused on startup snapshot integration which is more of a feature on its own, so rename it to "startup snapshot". Background: we are also considering adding a more generic performance initiative in nodejs/TSC#1343.
Review requested:
|
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
…47111) The initiative has been more focused on startup snapshot integration which is more of a feature on its own, so rename it to "startup snapshot". Background: we are also considering adding a more generic performance initiative in nodejs/TSC#1343.
This was landed without commit metadata, but that happened 13 hours ago and 2 other commits were landed on top of it. I don't know if we can still force-push... |
@targos can we enable GitHub's "Require status checks to pass before merging" and post a required status report that never passes to block the "merge" button? This still allows node-core-util to land commits since it pushes to the main branch directly. |
Not really. The commit queue uses the "squash and merge" button (with a GitHub API call) |
Also, if you require status checks to pass before merging, it becomes impossible to push a commit directly, as it wouldn't have the required check. |
good to know that. thanks for the explanation! |
…47111) The initiative has been more focused on startup snapshot integration which is more of a feature on its own, so rename it to "startup snapshot". Background: we are also considering adding a more generic performance initiative in nodejs/TSC#1343.
…47111) The initiative has been more focused on startup snapshot integration which is more of a feature on its own, so rename it to "startup snapshot". Background: we are also considering adding a more generic performance initiative in nodejs/TSC#1343.
…47111) The initiative has been more focused on startup snapshot integration which is more of a feature on its own, so rename it to "startup snapshot". Background: we are also considering adding a more generic performance initiative in nodejs/TSC#1343.
The initiative has been more focused on startup snapshot integration which is more of a feature on its own, so rename it to "startup snapshot".
Background: we are also considering adding a more generic performance initiative in nodejs/TSC#1343.