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

Upgrade churn #291

Merged
merged 1 commit into from
Apr 28, 2020
Merged

Upgrade churn #291

merged 1 commit into from
Apr 28, 2020

Conversation

jkeam
Copy link
Member

@jkeam jkeam commented Nov 3, 2016

Update version of churn

@jkeam
Copy link
Member Author

jkeam commented Nov 3, 2016

I was unable to reproduce #277 but worth updating our very old version of churn anyways.

Also hoping it fixes @trejkaz's issue.

@jkeam
Copy link
Member Author

jkeam commented Jul 12, 2017

Thoughts on this? Ok to merge?

@jkeam
Copy link
Member Author

jkeam commented Feb 27, 2018

Would anyone object to this being merged in?

@pboling
Copy link

pboling commented Feb 27, 2018

onward and upward!

@bronzdoc bronzdoc merged commit fbedb09 into metricfu:master Apr 28, 2020
@danmayer
Copy link

danmayer commented Apr 29, 2020

Hey, all awesome to see some activity on metric-fu... I haven't been doing much on churn lately, but I fixed a few issues at the 1.x jump... So I recommend the latest version. If anything in churn is causing issues please ping me on GitHub or twitter @danmayer I expect all the basics that metric-fu should work back till Ruby 2.3, while newer features like class and method churn are a bit less reliable. I am glad it is still working for y'all and this project, and I would love to be a bit more active if you all need anything.

  • churn author

@bronzdoc
Copy link

Thanks for the heads up @danmayer!

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