Skip to content

#3718: Added date to changelog #3727

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

Closed
wants to merge 5 commits into from
Closed

#3718: Added date to changelog #3727

wants to merge 5 commits into from

Conversation

irkartik
Copy link
Contributor

@irkartik irkartik commented Mar 4, 2018

This is my first pull request to readthedocs repo. Do guide me in case of any discrepency. Thank You :)

setup.cfg Outdated
@@ -1,6 +1,6 @@
[metadata]
name = readthedocs
version = 2.2.1
version = build
Copy link
Member

Choose a reason for hiding this comment

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

What is the implication in changing this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I didn't changed it.. It got automatically changed when i ran invoke prepare build ... Looks like I had to pass version number in place of build.

@@ -1,4 +1,4 @@
{{header}}
{{header}} - {{date}}
{{toHeader header "-"}}
Copy link
Member

Choose a reason for hiding this comment

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

The toHeader must receive the same above text, so that they have the same width

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do i need to re submit the code?

Copy link
Member

Choose a reason for hiding this comment

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

Just do the requested changes on this same branch and do push again, GitHub will update the PR automatically :). Let me know if you need more help.

CHANGELOG.rst Outdated
@@ -1,3 +1,48 @@
Version build - March 04, 2018
Copy link
Member

Choose a reason for hiding this comment

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

I think there is no need to add the changelog here, but looks great how is generated now :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you... But hope I didn't messed up anything in my first attempt :P

Copy link
Member

Choose a reason for hiding this comment

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

It's ok, just revert the version number, delete the changelog file and take a look to my other comment. Then I think it's ready to get merged! Thanks for you interest on collaborating.

@irkartik
Copy link
Contributor Author

hi @stsewd , I just wanted to know the status of this PR. Are there any additional changes to be made here?

@stsewd
Copy link
Member

stsewd commented Mar 13, 2018

@rajujha373 seems fine to me, we only need to wait to rtd team for a review. Can you upload a sample file of how the current changelog will look like?

@irkartik
Copy link
Contributor Author

screenshot from 2018-03-13 23-12-55

please have a look @stsewd

@@ -1,5 +1,6 @@
{{header}}
{{toHeader header "-"}}
Date: {{date}}
Copy link
Member

Choose a reason for hiding this comment

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

We need a newline before this

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Im so sorry but I have deleted the branch via which I had made changes. Shall I make a new pull request?

Copy link
Member

Choose a reason for hiding this comment

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

I think is better to continue the PR on this branch, so we don't lost the review... Maybe you don't have an option on the bottom like restore branch or something?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Im sorry but I think I've lost the branch that i worked upon.. its not showing in my repo 😢 are you sure I shall not create a new PR, because its just a single line of code that has been changed :(

Copy link
Member

Choose a reason for hiding this comment

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

Can you search if there is a way of restoring your previous branch first? Please. I see that all your PRs were affected. If not, making a new PR makes sense here.

Copy link
Contributor Author

@irkartik irkartik Mar 13, 2018

Choose a reason for hiding this comment

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

@stsewd I am sorry for the mess i've made here. even my PR on issue #3757 have been a mess because of this. I googled for the solution but was not able to find any. The main issue was that i deleted the forked repo from my profile (i know thats dumb). Please allow me a new PR and I will keep in mind these things in future. Again, I am so sorry for the inconvenience caused to you :(

Copy link
Member

Choose a reason for hiding this comment

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

Don't worry too much about that, it's fine creating a new PR and linking that one here.

Copy link
Member

@humitos humitos left a comment

Choose a reason for hiding this comment

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

Thanks!

I think we only need the extra line that @stsewd said and we are ready to merge.

@RichardLitt
Copy link
Member

Closing in favor of #3788. Thank you, @rajujha373, and thanks for sticking with it and figuring out the solution to the PR fiasco!

@irkartik
Copy link
Contributor Author

I should thank you guys for letting me continue with it ... lol @RichardLitt

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

Successfully merging this pull request may close these issues.

4 participants