Skip to content
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

content(learn): Profiling a Node.js application #7158

Merged
merged 5 commits into from
Nov 3, 2024

Conversation

Makena-Wambui
Copy link
Contributor

Description

I included a brief description of what Profiling a Node.js application means to give beginners a better perspective.

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npm run format to ensure the code follows the style guide.
  • I have run npm run test to check if all tests are passing.
  • I have run npx turbo build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.

@Makena-Wambui Makena-Wambui requested a review from a team as a code owner November 1, 2024 10:42
Copy link

vercel bot commented Nov 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Nov 1, 2024 10:45am

Copy link
Member

@mikeesto mikeesto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks

Copy link
Contributor

@AugustinMauroy AugustinMauroy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGMT ! thank for your contribution

@AugustinMauroy AugustinMauroy changed the title Profiling a Node.js application content(leanr): Profiling a Node.js application Nov 2, 2024
@AugustinMauroy AugustinMauroy changed the title content(leanr): Profiling a Node.js application content(learn): Profiling a Node.js application Nov 2, 2024
@mikeesto mikeesto added the github_actions:pull-request Trigger Pull Request Checks label Nov 3, 2024
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Nov 3, 2024
Copy link

github-actions bot commented Nov 3, 2024

Unit Test Coverage Report

Lines Statements Branches Functions
Coverage: 92%
90.54% (594/656) 76.27% (180/236) 94.35% (117/124)

Unit Test Report

Tests Skipped Failures Errors Time
134 0 💤 0 ❌ 0 🔥 5.558s ⏱️

@mikeesto mikeesto added this pull request to the merge queue Nov 3, 2024
Merged via the queue into nodejs:main with commit 845a142 Nov 3, 2024
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants