You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even worse in this case, it's two different casings for the same word which wrecks havoc in case-incentive environments like Macs
The crawler should, for project list types that aren't org, generate filenames in the for ${organization}--${repository} to ensure uniqueness. Rolling this out would generate a massive set of renames though that could break historical analysis. Maybe this expanded naming could be applied only when collisions are detected instead to minimize historical churn?
The text was updated successfully, but these errors were encountered:
For project lists other than github orgs, it's possible to have multiple projects with the same repo name
One such example exists under Hack for LA currently:
Even worse in this case, it's two different casings for the same word which wrecks havoc in case-incentive environments like Macs
The crawler should, for project list types that aren't org, generate filenames in the for
${organization}--${repository}
to ensure uniqueness. Rolling this out would generate a massive set of renames though that could break historical analysis. Maybe this expanded naming could be applied only when collisions are detected instead to minimize historical churn?The text was updated successfully, but these errors were encountered: