InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns

Monthly Metrics: New Issues + New Pull Requests 2026-08-01..2026-08-31

Aperta
#934 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@spier ci sta già lavorando.

Dal 1/9/2026.

community metrics
Lingua principale
HTML
Stelle
853
Fork
206
Merge medio
1g 23h
PR unite (30g)
2

Descrizione

Issue Metrics

Metric Average Median 90th percentile
Time to first response None None None
Time to first review None None None
Time to close None None None
Metric Count
Number of items that remain open 2
Number of items closed 0
Total number of items created 2
Title URL Assignee Author Time to first response Time to first review Time to close
Monthly Metrics: Contributors 2026-07-01..2026-07-31 https://github.com/InnerSourceCommons/InnerSourcePatterns/issues/922 spier github-actions[bot] None None None
Monthly Metrics: New Issues + New Pull Requests 2026-07-01..2026-07-31 https://github.com/InnerSourceCommons/InnerSourcePatterns/issues/921 spier github-actions[bot] None None None

This report was generated with the Issue Metrics Action
Search query used to find these items: repo:InnerSourceCommons/InnerSourcePatterns is:issue created:2026-08-01..2026-08-31 -reason:"not planned" -author:NewMexicoKid -author:WillemJiang -author:cewilliams -author:jrcosta -author:lenucksi -author:ovas04 -author:psanxiao -author:robtuley -author:spier -author:yuhattor -author:zilio


Issue Metrics

Metric Average Median 90th percentile
Time to first response 4 days, 6:09:00 22:51:36 10 days, 10:11:01
Time to first review 4 days, 19:21:54 3 days, 6:00:26 11 days, 1:55:54
Time to close 5 days, 17:35:05 6 days, 7:13:23 11 days, 17:40:56
Metric Count
Number of items that remain open 4
Number of items closed 5
Total number of items created 9
Title URL Assignee Author Time to first response Time to first review Time to close
Add patterns: Sponsor-Amplified Evangelism and Discovering Cross-Team Success Stories https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/933 None shrutibist None None None
Add pattern: Sponsor Communication and Engagement https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/932 None shrutibist None None None
Add pattern: Transparent Catalog of Privacy Controls and Posture https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/931 None shrutibist 22:51:36 None None
Bump the npm_and_yarn group across 1 directory with 3 updates https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/929 None dependabot[bot] 0:01:32 0:01:32 0:01:39
Fix link checker false positives on root-relative asset links https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/927 None rrrutledge 4:48:09 4:48:09 4:48:16
Add GitLab as Known Instance and draft Paired Onboarding Sprint pattern https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/926 None rrrutledge 4:17:13 4:17:13 None
Add analyze-innersource-video Claude Code skill https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/925 None rrrutledge 6 days, 7:12:44 6 days, 7:12:44 6 days, 7:13:23
Bump vale-cli/vale-action from 2 to 3 https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/924 None dependabot[bot] 7 days, 19:11:27 7 days, 19:11:27 7 days, 19:11:37
Bump ip-address from 10.2.0 to 10.4.0 in /pattern-categorization in the npm_and_yarn group across 1 directory https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/923 None dependabot[bot] 14 days, 8:40:21 14 days, 8:40:21 14 days, 8:40:29

This report was generated with the Issue Metrics Action
Search query used to find these items: repo:InnerSourceCommons/InnerSourcePatterns is:pr created:2026-08-01..2026-08-31 -reason:"not planned" -author:NewMexicoKid -author:WillemJiang -author:cewilliams -author:jrcosta -author:lenucksi -author:ovas04 -author:psanxiao -author:robtuley -author:spier -author:yuhattor -author:zilio

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.