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

[ci skip] Update contributing guide #19732

Merged
merged 1 commit into from
Apr 12, 2015
Merged

[ci skip] Update contributing guide #19732

merged 1 commit into from
Apr 12, 2015

Conversation

wazery
Copy link
Contributor

@wazery wazery commented Apr 11, 2015

Just mention the correct place for the new entries to the CHANGELOG.

@robin850
Copy link
Member

Hi @wazery,

Thanks for the patch. Actually the fact that new entries should be at the top is already mentioned in the lines under the one you edited. I think @matthewd meant that we should highlight it more. Maybe we should remove the "and it should got on top of a CHANGELOG" part of the sentence and add a whole new line after "you should attach the issue's number" like:

Make sure that new CHANGELOG entries get at the top of the file.

What do you think Matthew ?

@robin850 robin850 added the docs label Apr 11, 2015
@wazery
Copy link
Contributor Author

wazery commented Apr 11, 2015

Hi @robin850

+1 for a new line and emphasizing the "at the top" part of the sentence.

I can amend the commit after Matthew's opinion.

@matthewd
Copy link
Member

Hmm. I suspect this change would help as written, and we could just remove the now-redundant mention in the second paragraph. I actually looked for an "at the top" here last time I fixed one manually, and didn't see that it was already stated. 😥

@wazery
Copy link
Contributor Author

wazery commented Apr 11, 2015

@matthewd I will remove the second mention and emphasize the "at the top" part.

@wazery
Copy link
Contributor Author

wazery commented Apr 12, 2015

Edited the commit, I hope it can be merged now.


A CHANGELOG entry should summarize what was changed and should end with author's name and it should go on top of a CHANGELOG. You can use multiple lines if you need more space and you can attach code examples indented with 4 spaces. If a change is related to a specific issue, you should attach the issue's number. Here is an example CHANGELOG entry:
A CHANGELOG entry should summarize what was changed and should end with author's name. You can use multiple lines if you need more space and you can attach code examples indented with 4 spaces. If a change is related to a specific issue, you should attach the issue's number. Here is an example CHANGELOG entry:
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's fix this sentence too. There's a "the" missing in front of "author's".

Copy link
Contributor Author

@wazery wazery Apr 12, 2015 via email

Choose a reason for hiding this comment

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

kaspth added a commit that referenced this pull request Apr 12, 2015
[ci skip] Update contributing guide
@kaspth kaspth merged commit efaec3d into rails:master Apr 12, 2015
@kaspth
Copy link
Contributor

kaspth commented Apr 12, 2015

@wazery Thanks 😉

@wazery
Copy link
Contributor Author

wazery commented Apr 12, 2015

@kaspth 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants