Skip to content
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

Update README.md #17

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #17

wants to merge 1 commit into from

Conversation

bhuvi1114
Copy link

No description provided.

1. Fork it. (<https://github.com/yourname/yourproject/fork>)
2. Create your feature branch. (`git checkout -b feature/fooBar`)
3. Commit your changes. (`git commit -am 'Add some fooBar'`)
4. Push to the branch. (`git push origin feature/fooBar`)
Copy link

Choose a reason for hiding this comment

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

Why do you put full stop before parenthesis?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, if you want to dot those lines it should really be:

Text text ().

…or perhaps even better - commas, and a period on the last.

  1. Foo,
  2. Bar,
  3. Baz.

/2¢

Copy link

@MichaelCurrin MichaelCurrin Jul 6, 2020

Choose a reason for hiding this comment

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

Parentheses are unneeded if it is split over lines. Keep the full stop.

Example code:

2. Create your feature branch.
    ```sh
    git checkout -b feature/fooBar
    ```

Result:

  1. Create your feature branch.
    git checkout -b feature/fooBar

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.

4 participants