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

Fix inherits decorator docs. #1679

Merged
merged 1 commit into from
Jun 3, 2016
Merged

Conversation

pkaleta
Copy link
Contributor

@pkaleta pkaleta commented May 6, 2016

Description

Just a simple change to the description of how to use the inherits decorator. I think there was a bug in the class that's supplied as the argument to clone in the example used as the motivation for the inherits.

Have you tested this? If so, how?

No tests required, since it's just the docs fix.

@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @drj42, @erikbern and @steenzout to be potential reviewers

@Tarrasch
Copy link
Contributor

Tarrasch commented May 6, 2016

Cool! LGTM

@dlstadther
Copy link
Collaborator

@Tarrasch Is this good to be merged? Also, do you normally merge or squash?

@Tarrasch Tarrasch merged commit b274d16 into spotify:master Jun 3, 2016
@Tarrasch
Copy link
Contributor

Tarrasch commented Jun 3, 2016

Usually squash, and also reword it. I find the practice of rewording somebody else's commit message to be a very healthy check for myself that I actually understand what I'm merging. :)

However, if there are many commits, all clean and happening in a logical order that simplifies reviewing and perhaps reverting. I do a merge-commit as the value of the individual commits being merged are high.

This was referenced Jun 29, 2022
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