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
{{ message }}
Repository navigation
Commit 33bab2c
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: doc/architecture.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,6 +70,16 @@ flowchart LR
70
70
71
71
Candidate issues are enriched where possible with repository metadata, recent discussion, assignment state, linked pull requests, and Hacktoberfest signals. Repository health uses recent pushes, open issue and pull-request activity, stars, forks, and issue-tracker availability to distinguish active, moderate, and stale projects. The health score contributes a small optional boost to issue quality ranking and is shown directly on issue cards. The application ranks the enriched results for contributor relevance and returns paginated results to the browser.
72
72
73
+
Contribution readiness combines the existing repository health, maintainer
74
+
responsiveness, assignment, and discussion signals with GitHub's community
75
+
profile. Community-profile requests are limited to 12 repositories per search
76
+
and cached for six hours. The profile supplies README, contributing guide,
77
+
license, code-of-conduct, issue-template, and pull-request-template links.
78
+
Issue cards show an explainable readiness status and expandable checklist.
79
+
Unavailable profiles produce `Unknown` rather than a zero score; inactive,
80
+
claimed, and poorly documented opportunities remain distinguishable from issues
81
+
that are ready to start or should be discussed with maintainers first.
82
+
73
83
Maintainer responsiveness remains separate from repository health. For at most 12
74
84
candidate repositories per search, a cached six-hour GitHub GraphQL request samples
75
85
up to 20 recently updated issues and pull requests from the previous 90 days. The
@@ -100,6 +110,7 @@ Search filters currently include:
100
110
- Documentation, tests, bug fix, or feature contribution type
101
111
- All scopes or small scope
102
112
- Any, responsive, variable, slow, or unknown maintainer responsiveness
113
+
- Any readiness or Ready to start
103
114
104
115
Experience, contribution type, and scope classifications use explicit issue
105
116
labels and structured issue-template fields. Results show the signals that
@@ -249,6 +260,7 @@ erDiagram
249
260
text contribution_type
250
261
text scope
251
262
text responsiveness
263
+
text readiness
252
264
}
253
265
254
266
OPPORTUNITY {
@@ -370,6 +382,8 @@ contributing signals beside each repository. Weekly recommendations display the
370
382
same quality and repository-health scores used to rank results in the portal.
371
383
Repository alerts enrich their newest issues with repository health and the same
372
384
quality formula before adding the repository responsiveness boost.
385
+
Saved-search recommendations and weekly digest searches retain the selected
386
+
contribution-readiness filter, and weekly issue summaries include readiness.
373
387
Saved-search recommendations, repository alerts, repository metadata, and
374
388
post-delivery persistence run concurrently where independent so SMTP delivery is
375
389
not delayed by avoidable serial network or database round trips.
Copy file name to clipboardExpand all lines: doc/contributing.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,10 @@ The test suite uses Vitest. Coverage thresholds are configured in `vitest.config
35
35
36
36
## Database changes
37
37
38
-
Database changes must update both the Drizzle schema and a new ordered SQL migration. Migrations may be public because they describe structure, not credentials. Never include tokens, secrets, or production records in them.
38
+
Database changes must update the Drizzle schema, architecture documentation,
39
+
and a new ordered SQL migration. Migrations may be public because they describe
40
+
structure, not credentials. Never include tokens, secrets, or production records
The first migration creates Better Auth's user, session, account, and verification tables. The second creates user-owned saved searches. Migration files intentionally contain structure only—never credentials or production data.
57
58
@@ -78,6 +79,8 @@ searches. Existing records default to unrestricted responsiveness.
78
79
The eleventh stores dismissed recommendation feedback and repositories hidden
79
80
by a user. The twelfth adds private state, note, follow-up date, and workflow
80
81
activity fields to saved opportunities; existing opportunities begin in Saved.
82
+
The thirteenth adds the contribution-readiness preference to cloud saved searches;
83
+
existing records continue to include every readiness status.
0 commit comments