Fix git commit typo #1347
Fix git commit typo #1347
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/heptqao5t |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 5041399:
|
|
@Koooooo-7 I agree with you. I just included only the -m tag for message but didn't notice the add tag. So, yeah. I'll change in the code and say! |
Koooooo-7
requested review from
anikethsaha,
jhildenbiddle,
trusktr and
sy-records
| @@ -84,7 +84,7 @@ So that you can start straight away. | |||
|
|
|||
| - Fork it! | |||
| - Create your feature branch: `git checkout -b my-new-feature` | |||
| - Commit your changes: `git commit -am 'Add some feature'` | |||
| - Commit your changes: `git add . && git commit -m 'Add some feature'` | |||
There was a problem hiding this comment.
I think it's the same thing, but I always use git add.
There was a problem hiding this comment.
It is the same thing, but I didn't use this -am flag all time. So yeah!
There was a problem hiding this comment.
Basically, it is just a litte different that git commit -am wont commit those untracked files(the new files you create).
Summary
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx], where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.