Skip to content

Conversation

@legend80s
Copy link

liuchuanzong and others added 30 commits May 29, 2025 09:04
…eadme.md to main generated by npm run fix:eslint-docs using Node.js v22.16.0
…eadme.md to main generated by npm run fix:eslint-docs using Node.js v22.16.0
@legend80s
Copy link
Author

Can you fix the merge conflicts?

OK

@legend80s
Copy link
Author

@fisker Could you check the CI failures? They don’t appear to be related to this PR.

@fisker
Copy link
Collaborator

fisker commented Oct 16, 2025

#2782

Copy link
Collaborator

@fisker fisker left a comment

Choose a reason for hiding this comment

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

I'm having difficulty understanding the logic, will take another look.

@fisker
Copy link
Collaborator

fisker commented Oct 16, 2025

@legend80s
Copy link
Author

Please also take a look at https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/new-rule.md

I ran npm run fix:eslint-docs before, but the generated README.md tends to cause merge conflicts, so I suggest the merger run it after this PR is merged.

@legend80s legend80s requested a review from fisker October 21, 2025 01:43
@legend80s
Copy link
Author

@fisker Could you check the lint warnings for me. I have merge main but the warnings still exists:
https://github.com/sindresorhus/eslint-plugin-unicorn/actions/runs/18706642494/job/53345855996?pr=2661

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.

3 participants