Skip to content

refactor: Default bitness on the download page #6670

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

Merged
merged 1 commit into from
Apr 24, 2024

Conversation

canerakdas
Copy link
Member

Description

This PR contains the review changes suggested in #6614

Apart from this, I will check if we can keep the bitness information as a string to use it without editing everywhere with different PR. We add x before bitness when string and repeat the type checks everywhere

(I'm open to suggestions to make this easier 😄)

Validation

In the preview, download links should be correct

Related Issues

Related to #6613 #6614

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npx turbo format to ensure the code follows the style guide.
  • I have run npx turbo 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.

@canerakdas canerakdas requested a review from a team as a code owner April 24, 2024 17:10
Copy link

vercel bot commented Apr 24, 2024

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

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Apr 24, 2024 5:11pm

Copy link

@devlopersabbir devlopersabbir left a comment

Choose a reason for hiding this comment

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

looks like okay

Copy link
Member

@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.

LGTM

@ovflowd ovflowd added the github_actions:pull-request Trigger Pull Request Checks label Apr 24, 2024
@ovflowd ovflowd enabled auto-merge April 24, 2024 18:26
@ovflowd
Copy link
Member

ovflowd commented Apr 24, 2024

Welcome back, @canerakdas 🎉

Copy link
Contributor

github-actions bot commented Apr 24, 2024

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟠 80 🟢 100 🟢 100 🟢 91 🔗
/en/about 🟢 99 🟢 100 🟢 100 🟢 91 🔗
/en/about/previous-releases 🟢 97 🟢 98 🟢 100 🟢 92 🔗
/en/download 🟢 99 🟢 100 🟢 100 🟢 91 🔗
/en/blog 🟢 100 🟢 100 🟢 100 🟢 92 🔗

Copy link
Contributor

github-actions bot commented Apr 24, 2024

Unit Test Coverage Report

Lines Statements Branches Functions
Coverage: 91%
90.04% (588/653) 76.08% (175/230) 92.18% (118/128)

Unit Test Report

Tests Skipped Failures Errors Time
128 0 💤 0 ❌ 0 🔥 5.72s ⏱️

@ovflowd ovflowd disabled auto-merge April 24, 2024 19:12
@ovflowd ovflowd added the github_actions:pull-request Trigger Pull Request Checks label Apr 24, 2024
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Apr 24, 2024
@ovflowd ovflowd added this pull request to the merge queue Apr 24, 2024
Merged via the queue into nodejs:main with commit b092695 Apr 24, 2024
22 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.

5 participants