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

Fixed codeblock error 😉 #501

Closed
wants to merge 3 commits into from
Closed

Fixed codeblock error 😉 #501

wants to merge 3 commits into from

Conversation

0x48piraj
Copy link
Member

Fixes #499 👍

Changes made :-

  • Added :: 😊

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

  • I read the commit guidelines and I've followed
    them.
  • I ran coala over my code locally. (All commits have to pass
    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:

The more you review, the more your score will grow at coala.io and we will
review your PRs faster!

`::` was missing 😊
@@ -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.::
Copy link
Member

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 👍

Copy link
Member Author

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.

Copy link
Member

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::

Copy link
Member Author

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 ? 😊

Copy link
Member

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.

Copy link
Member

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:

Copy link
Member Author

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 😉

Copy link
Member Author

@0x48piraj 0x48piraj Nov 26, 2017

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. 😊

Copy link
Member

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 👍

Copy link
Member Author

Choose a reason for hiding this comment

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

I am sorry, But I'm on Web Interface, I will take care from the next time ! 😕
A maintainer can merge and squash the commits easily.

Reference : https://stackoverflow.com/questions/35948131/github-squash-commits-from-web-interface-on-pull-request-after-review-comments

@khanchi97
Copy link
Member

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

@prnvdixit
Copy link
Member

Also, fix your commit to adhere to https://coala.io/commit 😄

@0x48piraj
Copy link
Member Author

I am sorry, But I'm on Web Interface, I will take care from the next time ! 😕
A maintainer can merge and squash the commits easily.

Reference : https://stackoverflow.com/questions/35948131/github-squash-commits-from-web-interface-on-pull-request-after-review-comments

@jayvdb
Copy link
Member

jayvdb commented Nov 27, 2017

@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.
Our newcomer process exists only to ensure you know how to use git correctly.
If you dont follow our processes, we discard your PR.
Thank you.

@0x48piraj
Copy link
Member Author

0x48piraj commented Nov 27, 2017

Okay, I will do it all again 👍
But, I think you should have given me a chance, I said I will take care from next time.
I know how to use git, It's just that, the issue was so small that I used web-interface.

If you dont follow our processes, we discard your PR.

I never said anything @jayvdb , It was just a request.
Sorry. 😖

@prnvdixit
Copy link
Member

@0x48piraj

I think you should have given me a chance

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. 🎉
As far as using web interface is concerned - We all (and hopefully you too) contribute to OSS to get familiar with ideal practices both for actual coding as well as code management. So, preferably you should respond firmly to any reviews (or critical comments) rather than "I never said anything" 😉.
You might get away with using web interface for some of your issues but at the end of day, you might have to move to git to solve some complex ones - So, why not use it from start itself 😛.

I will do it all again

Also, it's a great first PR 😄 - you needn't start a new PR, just go through the suggested changes and associated guides 😃.

@0x48piraj
Copy link
Member Author

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 git 😛
And "I never said anything" was for that this was just a request to accept this PR, and from next issue, I will do it via git.
Anyways, you all are right! I read the guidelines, but of my laziness I did it via web-interface.
I know I'm assigned 😉
Thanks @prnvdixit for such a positive comment.
From now, I will do as it is done in coala 😊

Copy link
Contributor

@newbazz newbazz left a 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.

Copy link
Contributor

@newbazz newbazz left a 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

@newbazz
Copy link
Contributor

newbazz commented Jan 6, 2018

@0x48piraj are you still on this issue?

@0x48piraj
Copy link
Member Author

Actually No.
If they'll merge it as it is. Cool! Otherwise, You can work on this 👍

@newbazz
Copy link
Contributor

newbazz commented Jan 6, 2018

Sorry, but it cant be merged as it is.

@0x48piraj
Copy link
Member Author

🤣 Okay @newbazz. Go on 🚀

@0x48piraj 0x48piraj closed this Jan 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

coafile.rst: Fix bad setting example codeblock markup
7 participants