lucavallin/verto

Log repositories not matching requirements

Open

#206 opened on Oct 3, 2023

View on GitHubContributor guide
 (7 comments) (0 reactions) (0 assignees)TypeScript (95 forks)auto 404
data-generationenhancementgood first issuehelp wanted

Repository metrics

Stars
 (426 stars)
PR merge metrics
 (PR metrics pending)

Description

Since we have multiple reasons why a project is not added (namely stars count and issues count) and we have different places where we do filter those out (for GitHub is a mix of GraphQL query and manual filter, for GitLab is only manual filter).

Probably, a good way to handle this would do all the queries and then iterate over the repos coming from a source and see if it's there or not, and log those results.

Originally posted by @zillemarco in https://github.com/lucavallin/first-issue/pull/171#discussion_r1342371850

Contributor guide

Research direction
Implement logging for repositories that fail to meet requirements (stars count, issues count) by querying all repositories from each source first, then iterating over them to check conditions and log failures. This involves refactoring the current filtering logic to separate querying from validation, and adding logging for each exclusion reason.
Tech stack
typescript
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.jsGraphQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65