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

[12.0] account_analytic_cost_category #137

Merged
merged 5 commits into from
Oct 14, 2019

Conversation

AaronHForgeFlow
Copy link
Contributor

Supersedes #136

@codecov-io
Copy link

codecov-io commented Oct 14, 2019

Codecov Report

Merging #137 into 12.0 will increase coverage by 2.51%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##             12.0     #137      +/-   ##
==========================================
+ Coverage   59.42%   61.94%   +2.51%     
==========================================
  Files          25       28       +3     
  Lines         663      741      +78     
==========================================
+ Hits          394      459      +65     
- Misses        269      282      +13
Impacted Files Coverage Δ
...c_cost_category/models/account_analytic_account.py 100% <100%> (ø)
...rogress_measurement/models/progress_measurement.py 84% <0%> (ø)
...ss_measurement/models/progress_measurement_type.py 81.63% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 727dc80...81a4e3c. Read the comment docs.

@AaronHForgeFlow
Copy link
Contributor Author

autoapprove

@AaronHForgeFlow AaronHForgeFlow merged commit bb636e4 into 12.0 Oct 14, 2019
@AaronHForgeFlow AaronHForgeFlow deleted the 12.0-account_analytic_cost_category branch October 14, 2019 10:26
@bjeficent bjeficent mentioned this pull request Oct 14, 2019
51 tasks
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

3 participants