Skip to content

Conversation

@aduh95
Copy link
Contributor

To fix the linter on main

@aduh95aduh95 added the fast-track PRs that do not need to wait for 48 hours to land. label Jan 7, 2025
@aduh95aduh95 requested a review from ruyadornoJanuary 7, 2025 20:40
@github-actions
Copy link
Contributor

Fast-track has been requested by @aduh95. Please 👍 to approve.

@nodejs-github-botnodejs-github-bot added the doc Issues and PRs related to the documentations. label Jan 7, 2025
@aduh95aduh95 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 Jan 7, 2025
@nodejs-github-botnodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Jan 7, 2025
@nodejs-github-botnodejs-github-bot merged commit 5119049 into nodejs:mainJan 7, 2025
30 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 5119049

@aduh95aduh95 deleted the fix-linter branch January 7, 2025 22:18
ruyadorno added a commit to nodejs/node-core-utils that referenced this pull request Jan 8, 2025
After two consecutive releases in which I mistakely pushed a broken release commit to main, I'm convinced that the process needs improvement. This changeset proposes to add a reminder to `git node release promote` to lint markdown files prior to pushing branches to upstream remote. Refs: nodejs/node@a344300 Refs: nodejs/node#56508
ruyadorno added a commit to nodejs/node-core-utils that referenced this pull request Jan 8, 2025
After two consecutive releases in which I mistakely pushed a broken release commit to main, I'm convinced that the process needs improvement. This changeset proposes to add a reminder to `git node release promote` to lint markdown files prior to pushing branches to upstream remote. Refs: nodejs/node@a344300 Refs: nodejs/node#56508
@targostargos 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. labels Jan 13, 2025
Ceres6 pushed a commit to Ceres6/node that referenced this pull request Jan 13, 2025
PR-URL: nodejs#56508 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.docIssues and PRs related to the documentations.dont-land-on-v20.xPRs that should not land on the v20.x-staging branch and should not be released in v20.x.dont-land-on-v22.xPRs that should not land on the v22.x-staging branch and should not be released in v22.x.fast-trackPRs that do not need to wait for 48 hours to land.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@aduh95@nodejs-github-bot@lpinca@MoLow@targos