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

Exclude bounties reserved for specific users from new bounties email #4426

Merged
merged 5 commits into from
May 31, 2019

Conversation

acolytec3
Copy link
Contributor

@acolytec3 acolytec3 commented May 17, 2019

Description

The current new bounties email includes bounties reserved for specific users which is annoying because reserved bounties aren't actually actually available to the general Gitcoin population. This PR adds an exclusion rule to the query that pulls relevant bounties to ensure that only bounties a user can actually apply for are included.

Refers/Fixes

Addresses one element of #4308

Testing

Adds new test for new_bounties_email.py that incorporates test for new exclusion of reserved bounties from email.

@codecov
Copy link

codecov bot commented May 17, 2019

Codecov Report

Merging #4426 into master will increase coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4426      +/-   ##
==========================================
+ Coverage   30.13%   30.13%   +<.01%     
==========================================
  Files         208      208              
  Lines       16787    16784       -3     
  Branches     2254     2253       -1     
==========================================
  Hits         5058     5058              
+ Misses      11535    11532       -3     
  Partials      194      194
Impacted Files Coverage Δ
...arketing/management/commands/new_bounties_email.py 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 4ec26ba...5069bfb. Read the comment docs.

@codecov
Copy link

codecov bot commented May 17, 2019

Codecov Report

Merging #4426 into master will increase coverage by 0.14%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4426      +/-   ##
==========================================
+ Coverage   30.02%   30.17%   +0.14%     
==========================================
  Files         209      209              
  Lines       16886    16886              
  Branches     2278     2278              
==========================================
+ Hits         5070     5095      +25     
+ Misses      11619    11594      -25     
  Partials      197      197
Impacted Files Coverage Δ
...arketing/management/commands/new_bounties_email.py 53.33% <ø> (+53.33%) ⬆️
app/dashboard/models.py 56.63% <0%> (+0.06%) ⬆️

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 4a0f127...f5eb732. Read the comment docs.

@acolytec3 acolytec3 changed the title Exclude bounties reserved for specific users from new bounties email Exclude bounties reserved for specific users from new bounties email -WIP May 17, 2019
@acolytec3 acolytec3 changed the title Exclude bounties reserved for specific users from new bounties email -WIP Exclude bounties reserved for specific users from new bounties email May 17, 2019
Copy link
Contributor

@danlipert danlipert left a comment

Choose a reason for hiding this comment

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

Looks great! Just one note on the throwaway variables (take it or leave it, just my preference) and then the 3-space indent changes and we should be good to go. Nice work with the test!

@danlipert danlipert merged commit f0439bb into gitcoinco:master May 31, 2019
@acolytec3
Copy link
Contributor Author

acolytec3 commented May 31, 2019 via email

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