-
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 issue #164 #165
Fixed issue #164 #165
Conversation
Thanks for your contribution! Reviewing pull requests take really a lot of time and we're all volunteers. Please make sure you go through the following check list and complete them all before pinging someone for a review.
As you learn things over your Pull Request please help others on the chat and on PRs to get their stuff right as well! |
Please amend the commit to meet the guidelines of https://coala.readthedocs.io/en/latest/Developers/Writing_Good_Commits.html Essentially, you have to have the short log something more better then just |
|
||
The first thing you should do is check other developers' pull requests to get the | ||
hang of things. | ||
You should also start working on low level issues or help us with artwork, tweets, etc. |
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 should also start working on low level issues or help us with artwork, tweets, etc.
You should also start working on low level difficulty/low
labelled issues or help us with artwork, tweets, etc.
The first thing you should do is check other developers' pull requests to get the | ||
hang of things. | ||
You should also start working on low level issues or help us with artwork, tweets, etc. | ||
|
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.
Same as requested above.
Notes haver been added to help necomers start fixing issues in the project. Fixes: coala#164
Thanks for your contribution! Reviewing pull requests take really a lot of time and we're all volunteers. Please make sure you go through the following check list and complete them all before pinging someone for a review.
As you learn things over your Pull Request please help others on the chat and on PRs to get their stuff right as well! |
Fixed the commit style to follow the guidelines. |
.. note:: | ||
|
||
The first thing you should do is check other developers' pull requests to get the | ||
hang of things. |
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.
I wouldn't recommend this as the first thing, first make a PR and then take a look at others, not only looking but also helping. Learning together with the others.
IMO though.
|
||
The first thing you should do is check other developers' pull requests to get the | ||
hang of things. | ||
You should also start working on difficulty/low labelled issues or help us with artwork, tweets, etc. |
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.
this sounds a bit vague, also I'd rather make like a strong recommendation to do this after they did the newcomer issue
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.
Also the language could be a little more harsh. This doesn't mention anything about reviewers spending a lot of time on these things.
|
||
The first thing you should do is check other developers' pull requests to get the | ||
hang of things. | ||
You should also start working on difficulty/low labelled issues or help us with artwork, tweets, etc. |
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.
same here
Btw. you seem to have two commits now, we only want one, riht? A rebase can help you. Here's the rebase instructions: it looks like your PR is out of date and needs a rebase. This page may help you to get started on this. (Do not press the update branch button. It's evil.) Add the original coala repository as a remote:
Then go to your branch and rebase it onto our master:
Here you can squash your commits! Now push it up. You will need to do a force push because you change history here (do not do this on master branches :)):
If you're just looking to fix an issue very quickly and not interested in contributing to coala long term, we can fix it up for you - just tell us :). Ping us on our gitter channel if you need help! |
Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again! |
3 similar comments
Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again! |
Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again! |
Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again! |
Still working on this ? @paurisa |
Isn't the issue already fixed? It says that it has already been closed so I thought it was fixed. |
Yes, It is fixed. You should close this PR. :) |
Closing it then. |
In case you haven't done any newcomer issue, then do one newcomer issue. Otherwise move to solve a difficulty : low issue. @paurisa |
I have added as notes the information asked in the issue #164