-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix: remove commit hint when no git repo was initialized #1502
Conversation
🦋 Changeset detectedLatest commit: 06729e9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@Mvmo is attempting to deploy a commit to the t3-oss Team on Vercel. A member of the Team first needs to authorize it. |
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://create-t3-app-git-fork-mvmo-next-t3-oss.vercel.app/ |
Had some problems with my local dev setup, didn't receive linting errors 😅 |
This is fixing a similar thing as #1507 but will conflict quite a bit. Will merge 1 and then the other will have to resolve some stuff |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conflicts
Actually don't think we need this after #1507 that prompts you to initialze a git repo if you aren't in one already. |
Closes #
✅ Checklist
Changelog
I've passed the noGit Option to the logNextSteps function and depending on that either logged the 'git commit -m "initial commit"' message or not
Screenshots
With git repo
Without git repo
💯