Skip to content

fix: "set up" as verb#1848

Closed
DePasqualeOrg wants to merge 1 commit intohuntabyte:mainfrom
DePasqualeOrg:set-up-as-verb
Closed

fix: "set up" as verb#1848
DePasqualeOrg wants to merge 1 commit intohuntabyte:mainfrom
DePasqualeOrg:set-up-as-verb

Conversation

@DePasqualeOrg
Copy link
Copy Markdown
Contributor

@DePasqualeOrg DePasqualeOrg commented Apr 22, 2025

"set up" is a verb, and "setup" is a noun.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 22, 2025

⚠️ No Changeset found

Latest commit: dde24e2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 30, 2025

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
shadcn-svelte ✅ Ready (View Log) Visit Preview dde24e2

Copy link
Copy Markdown
Owner

@huntabyte huntabyte left a comment

Choose a reason for hiding this comment

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

Thank you! May be a while before we merge this as not in the mood to deal with a bunch of merge conflicts at the moment with the next and tailwind 4 branches!

@AdrianGonz97
Copy link
Copy Markdown
Collaborator

I think we'll keep it the way it is in main. However, you feel up for it, feel free to make the changes to the next branch!

@DePasqualeOrg
Copy link
Copy Markdown
Contributor Author

@AdrianGonz97, I will create another PR for the next branch, but why not just merge this into main? LLMs consistently reproduce this mistake, especially in code comments and function names, because it's so prevalent in repos like this.

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