Skip to content

Start renaming res to result #5356

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

Merged
merged 1 commit into from
Jan 15, 2022
Merged

Start renaming res to result #5356

merged 1 commit into from
Jan 15, 2022

Conversation

canyon289
Copy link
Member

Minor change, but even though it is I think its worth it. The idea is to remove as many friction points as possible for new developers.

If this PR is merged will open an issue ticket for others to rename the other instances, as this will also make a good issue ticket for Data Umbrella sprint

@codecov
Copy link

codecov bot commented Jan 15, 2022

Codecov Report

Merging #5356 (2a44c7a) into main (1a0b1e9) will decrease coverage by 0.02%.
The diff coverage is 90.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #5356      +/-   ##
==========================================
- Coverage   80.36%   80.34%   -0.03%     
==========================================
  Files          89       89              
  Lines       14805    14805              
==========================================
- Hits        11898    11895       -3     
- Misses       2907     2910       +3     
Impacted Files Coverage Δ
pymc/blocking.py 95.12% <85.71%> (ø)
pymc/math.py 68.68% <100.00%> (ø)
pymc/parallel_sampling.py 86.71% <0.00%> (-1.00%) ⬇️

@michaelosthege michaelosthege merged commit 2634f41 into main Jan 15, 2022
@michaelosthege michaelosthege deleted the res_rename branch January 15, 2022 15:22
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.

2 participants