Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Contribution cron job #70
base: main
Are you sure you want to change the base?
Contribution cron job #70
Changes from all commits
78c9012
62c2baa
0a03023
bdf353c
6a82561
4a3ddce
69da6c5
1eed590
d2bb998
b036c6a
b08a9a7
c517f2b
25492e0
39dcc5a
c3c265e
5bbfbd3
a0e1dde
e663a99
899f7a2
56a62fc
46ab775
d98005e
bf9c8a1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are we saving
profile.username
twice? If it's the same value, let's either rename the original or use that where you're usinggithubUsername
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need both fields because one field is the name we use for our application (their profile page, future banners, etc). We currently allow them to change this name so if their github username is something nonsensical they can change their name in our system. We need to know their actual githubUsername as well becuase graphql only retruns usernames, it does not return githubIds. So we need to know the username to match up contributions to the correct user. We update this username everytime they log in on line 90 or 106, becuase it is possible for them to update thier githubUsername.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the purpose of adding this here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To save the update to the gitHubUsername field above it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we aren't using this elsewhere, let's remove the
let
definition up top and make it aconst
hereThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are using it on line around line 141 for the contribution poll. It needs access to an entity manager