SasView event dashboard
Progress through the event
Running totals by day.
Where the closed PRs came from
Every PR merged or closed during the event, by when it was opened and whether it got new commits during the event.
How issues were closed
Closed by a merged PR or commit, versus closed by hand (triage, duplicates, already fixed).
— event PRs carry an AI co-author trailer (Claude, Copilot and similar).
Backlog: start of event → now
Open issues and pull requests in each repo when the event started, and now.
| Repo | Open issues | Change | Open PRs | Change |
|---|
Tests and docstrings: start of event → now
Measured on each repo's main branch and its active development branches. Includes work written earlier and merged during the event.
| Repo | Branch | Test functions | Change | Docstring coverage | Change |
|---|
Review queue
PRs opened or worked on during the event, not drafts, with no review yet. For PRs opened during the event, the median time to first review is — hours and to merge — hours.
| PR | Title | Author | Opened | Lines changed | Hours waiting |
|---|
First contributions
People whose first-ever PR to these repos was opened during the event.
| Contributor | PR | Title | Status |
|---|
By repository
Event activity per repo.
| Repo | PRs opened | Merged | Issues opened | Issues closed | Commits | Reviews |
|---|
CI on tracked branches
Latest run of each workflow on the branches measured above (not PR runs).
| Repo | Branch | Workflow | Status | Last run |
|---|
Since the last release
Commits on each repo's main branch that are not yet in a release.
| Repo | Latest release | Commits since | Of which during event |
|---|
How these numbers are counted
- Event window
- From 00:00 on the first day to 24:00 on the last day, in the event's time zone. All activity in the window counts, remote contributions included; bot accounts (Dependabot, pre-commit) are left out.
- New work, merged
- PR opened during the event and merged.
- Older PR reworked, merged
- PR opened before the event that got new commits during it and was merged.
- Backlog PR merged as-is
- PR opened before the event, merged after review with no new commits.
- Older PR closed (cleanup)
- PR opened before the event and closed without merging.
- Commits
- Non-merge commits authored during the event, on the default branch or on any PR branch active during the event, each counted once.
- Issue closed by a PR
- The closing event names a commit, or a merged PR referencing the issue landed within ten minutes of it closing.
- Backlog
- Open issues and PRs at 00:00 on the first day, compared with now (or the end of the event). An issue reopened after being closed counts by its latest close.
- Tracked branches
- The default branch, plus protected branches that are not release branches and had commits during the event (for example refactor_24). An event file can list branches explicitly.
- Test functions
- Python functions named test… anywhere in the repo, on the last commit before the event and the latest commit. sasmodels' per-model test tables are not counted.
- Docstring coverage
- Measured with interrogate on each repo's source folder (set in the event file), using the repo's own interrogate settings where it has them.
- Typical week
- Average over the weeks before the event (set per event).
- Contributors
- Anyone who opened a PR or issue, authored a commit or submitted a review in the window.
- Not counted
- Discussions, breakouts, wiki edits and PR comments that are not reviews.
Source and instructions for adding an event: SasView/event-dashboard.