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 issue #164 #165

Closed
wants to merge 2 commits into from
Closed

Fixed issue #164 #165

wants to merge 2 commits into from

Conversation

prisas
Copy link

@prisas prisas commented Oct 8, 2016

I have added as notes the information asked in the issue #164

@gitmate-bot
Copy link

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!

@meetmangukiya
Copy link
Member

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 Fixed issue #165


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.
Copy link
Member

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.

Copy link
Member

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
@gitmate-bot gitmate-bot added size/S and removed size/XS labels Oct 8, 2016
@gitmate-bot
Copy link

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!

@prisas
Copy link
Author

prisas commented Oct 8, 2016

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.
Copy link
Member

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.

CC @Adrianzatreanu @adtac


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.
Copy link
Member

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

Copy link
Member

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.
Copy link
Member

Choose a reason for hiding this comment

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

same here

@sils
Copy link
Member

sils commented Oct 8, 2016

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:

git remote add upstream https://github.com/coala/documentation.git

Then go to your branch and rebase it onto our master:

git checkout <yourbranch>
git fetch upstream
git rebase --interactive upstream/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 :)):

git push --force

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!

@gitmate-bot
Copy link

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
@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@aptrishu
Copy link
Member

aptrishu commented Oct 23, 2016

Still working on this ? @paurisa
It has been a long time we haven't seen any update from you.

@prisas prisas closed this Oct 23, 2016
@prisas
Copy link
Author

prisas commented Oct 23, 2016

Isn't the issue already fixed? It says that it has already been closed so I thought it was fixed.
#164

@prisas prisas reopened this Oct 23, 2016
@aptrishu
Copy link
Member

aptrishu commented Oct 23, 2016

Yes, It is fixed. You should close this PR. :)

@prisas
Copy link
Author

prisas commented Oct 23, 2016

Closing it then.

@prisas prisas closed this Oct 23, 2016
@Nosferatul
Copy link
Member

@aptrishu
Copy link
Member

In case you haven't done any newcomer issue, then do one newcomer issue. Otherwise move to solve a difficulty : low issue. @paurisa

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.

7 participants