-
Notifications
You must be signed in to change notification settings - Fork 178
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
Fixed codeblock
error 😉
#501
Conversation
`::` was missing 😊
Users/coafile.rst
Outdated
@@ -93,7 +93,7 @@ This is the same file without section inheritance:: | |||
All settings must be part of a section, so don't do this for implicit | |||
inheritance (this is also deprecated behavior). Implicit inheritance | |||
was leading to a section automatically getting inherited to all other | |||
sections without semantically making sense. | |||
sections without semantically making sense.:: |
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.
@0x48piraj Remove trailing period, then it will look fine 👍
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.
But, everywhere the same pattern is followed.
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.
Yeah, that's what I'm saying, everywhere the pattern should be same.But in your case, it should be like this
sections without semantically making sense::
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.
There's a full-stop at the last of sentence, so I left it. Should I remove the full-stop ? 😊
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.
yes, that's what I'm talking about.
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.
yes, and it should look like this making sense:
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.
No @khanchi97 , making sense:
reverts the whole issue back to zero 😉
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.
And, making sense::
does - making sense.:
I think my first commit was OK. 😊
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.
If you code like this making sense::
then it will look like making sense:
that you have done already.Now you only have to squash your commits 👍
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.
You also have to squash your commits.If you don't know how to squash commits then follow this link http://api.coala.io/en/latest/Developers/Git_Basics.html#squashing-your-commits |
Also, fix your commit to adhere to https://coala.io/commit 😄 |
@0x48piraj, please follow the instructions given to you by our developers. We have good reasons for why and how we do things, which you will learn if you proceed through the newcomer process. |
Okay, I will do it all again 👍
I never said anything @jayvdb , It was just a request. |
You are still assigned to the issue - Nobody would or can take up a issue from you unless you are not working on it anymore. 🎉
Also, it's a great first PR 😄 - you needn't start a new PR, just go through the suggested changes and associated guides 😃. |
I was talking about setting up the project in |
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.
You have three commits for the same issue, this sud not be the case one commit for each issue as per the newcomers guide. So kindly squash your commits to one.
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.
Always use 'git commit --amend' after the first commit
@0x48piraj are you still on this issue? |
Actually No. |
Sorry, but it cant be merged as it is. |
🤣 Okay @newbazz. Go on 🚀 |
Fixes #499 👍
Changes made :-
::
😊For short term contributors: we understand that getting your commits well
defined like we require is a hard task and takes some learning. If you
look to help without wanting to contribute long term there's no need
for you to learn this. Just drop us a message and we'll take care of brushing
up your stuff for merge!
Checklist
them.
individually. It is not sufficient to have "fixup commits" on your PR,
our bot will still report the issues for the previous commit.) You will
likely receive a lot of bot comments and build failures if coala does not
pass on every single commit!
After you submit your pull request, DO NOT click the 'Update Branch' button.
When asked for a rebase, consult coala.io/rebase
instead.
Please consider helping us by reviewing other peoples pull requests as well:
cobot mark wip <URL>
to get it outof the review queue.
The more you review, the more your score will grow at coala.io and we will
review your PRs faster!