Handle 404s when fetching GitHub user details
What does this MR do and why?
Handle 404s when fetching GitHub user details
The GitHub API can return a 404
when we try to fetch the user's
details. We can see some errors when importing rails/rails
.
Specifically for the user Copilot
.
We already have in place a fallback of using the GitHub username as the source user's name if we're unable to get the username from the API response.
This change does the same if we receive a 404
from the GitHub API.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
How to set up and validate locally
- Enable
github_user_mapping
feature flag. - Conduct a GitHub import with user contributions from Copilot.
- The source user should be created successfully with user name "Copilot"
Related to #508720 (closed)
Edited by Luke Duncalfe
Merge request reports
Activity
Please register or sign in to reply