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

Relative File Volatility by Commits (RFVC) #298

Merged
merged 9 commits into from
May 3, 2024
Merged

Conversation

IlnurHA
Copy link
Contributor

@IlnurHA IlnurHA commented May 3, 2024

This PR is adding new metric (RFVC) (Issue #128). In the issue you mentioned Relative File Volatility by Hits, but I think it would be better to create separate issue to implement this metric

@IlnurHA
Copy link
Contributor Author

IlnurHA commented May 3, 2024

@yegor256 Please, check this PR

@yegor256
Copy link
Owner

yegor256 commented May 3, 2024

@IlnurHA looks very good! please, run make lint locally. I'm sure, shellcheck will complain

@IlnurHA
Copy link
Contributor Author

IlnurHA commented May 3, 2024

@yegor256 It seems that all checks are passed in make section. Please check these changes


printf "class Foo {}" > "${java3}"
git add "${java3}"
git commit --quiet -m "-third commit"
Copy link
Owner

Choose a reason for hiding this comment

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

@IlnurHA try to make a few additional commits here and check the result of the metric, just to make sure it gives correct values

@IlnurHA
Copy link
Contributor Author

IlnurHA commented May 3, 2024

@yegor256 I added more commits as requested and more checks just to be sure that everything is correctly calculated. Can you check please?

@yegor256 yegor256 merged commit b621604 into yegor256:master May 3, 2024
10 checks passed
@yegor256
Copy link
Owner

yegor256 commented May 3, 2024

@IlnurHA thanks a lot!

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.

None yet

2 participants