Skip to content

Conversation

@aduh95
Copy link
Contributor

@aduh95 aduh95 commented Apr 29, 2025

As specified in https://no-color.org/, setting the env variable to an empty string should result in that env variable to be ignored:

Command-line software which adds ANSI color to its output by default should check for a NO_COLOR environment variable that, when present and not an empty string (regardless of its value), prevents the addition of ANSI color.

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. tty Issues and PRs related to the tty subsystem. labels Apr 29, 2025
@codecov
Copy link

codecov bot commented Apr 29, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.07%. Comparing base (eaebfab) to head (7c978b8).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #58074      +/-   ##
==========================================
- Coverage   90.09%   90.07%   -0.02%     
==========================================
  Files         640      640              
  Lines      188450   188450              
  Branches    36966    36962       -4     
==========================================
- Hits       169789   169752      -37     
- Misses      11364    11396      +32     
- Partials     7297     7302       +5     
Files with missing lines Coverage Δ
lib/internal/tty.js 99.23% <100.00%> (ø)

... and 33 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@BridgeAR BridgeAR added the semver-major PRs that contain breaking changes and should be released in the next major version. label Apr 29, 2025
@aduh95
Copy link
Contributor Author

aduh95 commented Apr 29, 2025

@BridgeAR is it semver-major or just a fix? Wdyt about not landing it on LTS release lines to minimize the risk of ecosystem breakage, but still land it on Current release line?

@BridgeAR
Copy link
Member

@aduh95 I think it's fine to land it on 24 or do you mean any release before?

@aduh95 aduh95 added dont-land-on-v18.x dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. and removed semver-major PRs that contain breaking changes and should be released in the next major version. dont-land-on-v18.x labels Apr 30, 2025
@BridgeAR BridgeAR added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. labels May 3, 2025
@nodejs-github-bot nodejs-github-bot added commit-queue-failed An error occurred while landing this pull request using GitHub Actions. and removed commit-queue Add this label to land a pull request using GitHub Actions. labels May 3, 2025
@nodejs-github-bot
Copy link
Collaborator

Commit Queue failed
- Loading data for nodejs/node/pull/58074
✔  Done loading data for nodejs/node/pull/58074
----------------------------------- PR info ------------------------------------
Title      tty: treat empty `NO_COLOR` same as absent `NO_COLOR` (#58074)
   ⚠  Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch     aduh95:fix-no-color -> nodejs:main
Labels     tty, author ready, needs-ci, dont-land-on-v20.x, dont-land-on-v22.x, dont-land-on-v23.x
Commits    4
 - tty: treat empty `NO_COLOR` same as absent `NO_COLOR`
 - fixup! tty: treat empty `NO_COLOR` same as absent `NO_COLOR`
 - Revert "fixup! tty: treat empty `NO_COLOR` same as absent `NO_COLOR`"
 - fixup! tty: treat empty `NO_COLOR` same as absent `NO_COLOR`
Committers 1
 - Antoine du Hamel <[email protected]>
PR-URL: https://github.com/nodejs/node/pull/58074
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/58074
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
--------------------------------------------------------------------------------
   ℹ  This PR was created on Tue, 29 Apr 2025 10:23:00 GMT
   ✔  Approvals: 3
   ✔  - Luigi Pinca (@lpinca): https://github.com/nodejs/node/pull/58074#pullrequestreview-2803306357
   ✔  - Michaël Zasso (@targos) (TSC): https://github.com/nodejs/node/pull/58074#pullrequestreview-2803318306
   ✔  - Ruben Bridgewater (@BridgeAR) (TSC): https://github.com/nodejs/node/pull/58074#pullrequestreview-2813243352
   ✘  Last GitHub CI failed
   ✘  No Jenkins CI runs detected
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/14811753178

@aduh95 aduh95 added request-ci Add this label to start a Jenkins CI on a PR. and removed commit-queue-failed An error occurred while landing this pull request using GitHub Actions. labels May 3, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label May 3, 2025
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@BridgeAR
Copy link
Member

BridgeAR commented Jun 2, 2025

@aduh95 this has some conflicts. It could otherwise likely land.

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@aduh95 aduh95 merged commit afbf2f3 into nodejs:main Jun 28, 2025
52 of 53 checks passed
@aduh95
Copy link
Contributor Author

aduh95 commented Jun 28, 2025

Landed in afbf2f3

@aduh95 aduh95 deleted the fix-no-color branch June 28, 2025 13:41
targos pushed a commit that referenced this pull request Jul 3, 2025
PR-URL: #58074
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. needs-ci PRs that need a full CI run. tty Issues and PRs related to the tty subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants