iseewhatyoudid 0.1.0__tar.gz

iseewhatyoudid-0.1.0/AI_POLICY.md

@@ -0,0 +1,15 @@
+# AI Contribution Policy
+
+We accept AI-*assisted* contributions, both for code and documentation, with the following expectations:
+
+- AI-assisted contributions must disclaim their use of AI.
+- Contributors must fully understand the proposed changes and be able to explain why they are the correct approach.
+- Issues must be created before creating pull requests (unless there is already a relevant issue).
+- Issue and pull request templates must be followed.
+- Comments (including bodies) in issues and pull requests must be written by humans. If you use LLMs to translate from one language to another, please include your original comment and the translated one.
+- Git commits must be authored by humans, not AI/bot accounts or identities.
+- Git commit messages must be written by humans, in English. If you cannot write English, please state so in the pull request body and we will write the commit messages ourselves.
+
+Failure to comply with any of these requirements will result in issues or pull requests being closed immediately without comment. Repeated violations of this policy will result in a ban of the offending accounts/identities from contributing to this project and any related project from the same author/organization.
+
+We do not accept AI-generated content in community spaces we maintain or moderate, such as GitHub discussions or Matrix rooms.

iseewhatyoudid-0.1.0/CHANGELOG.md

@@ -0,0 +1,43 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
+and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
+
+<!-- insertion marker -->
+## [0.1.0](https://github.com/pawamoy/iseewhatyoudid/releases/tag/0.1.0) - 2026-10-06
+
+<small>[Compare with first commit](https://github.com/pawamoy/iseewhatyoudid/compare/f9a5664bcecb539cc2f3278626f2120c3a64e3c4...0.1.0)</small>
+
+### Build
+
+- Drop support for Python 3.10 ([6e2997e](https://github.com/pawamoy/iseewhatyoudid/commit/6e2997e46d9a53bcd6382eee418ee2c25108f433) by Timothée Mazzucotelli).
+
+### Features
+
+- Initial implementation ([f9a5664](https://github.com/pawamoy/iseewhatyoudid/commit/f9a5664bcecb539cc2f3278626f2120c3a64e3c4) by Timothée Mazzucotelli).
+
+
+## Unreleased
+
+### Added
+
+- Add repeatable `--repos-dir` and `--commit-author-email` options to analyze
+  extensive public default-branch commit history from local clones.
+- Disclose full-clone local, shallow local, and bounded GitHub commit-summary
+  sources in the HTML dashboard.
+
+### Changed
+
+- Prefer incrementally cached local Git history over GitHub commit-summary
+  requests for matched, confirmed-public repositories.
+- Limit local history to the newest 2,000 matching commits per repository.
+- Discover all scoped GitHub clones instead of restricting local history to
+  repositories present in GitHub's contribution groups.
+- Continue clone discovery below a selected directory that is itself a Git
+  repository, and report progress while inspecting local remotes.
+- Restrict local clone mapping to `origin`, ignoring contributor and pull-request
+  remotes.
+- Remove the commit-scope chart and exclude merge commits with default subjects
+  from commit-summary analysis.

iseewhatyoudid-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at dev@pawamoy.fr. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+

iseewhatyoudid-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,112 @@
+# Contributing
+
+Contributions are welcome, and they are greatly appreciated. Every little bit helps, and credit will always be given.
+
+**Please always create an issue before working on a new feature or a bug fix, so that we can discuss the implementation and make sure that your work will be merged.**
+
+## Environment setup
+
+Install [uv](https://github.com/astral-sh/uv) and [direnv](https://direnv.net/), fork and clone the repository, then:
+
+```bash
+cd iseewhatyoudid
+direnv allow
+make setup
+```
+
+You now have the dependencies installed.
+
+You can run the application with `make run iseewhatyoudid [ARGS...]`.
+
+Run `make help` to see all the available actions!
+
+## Tasks
+
+The entry-point to run commands and tasks is the `make` Python script, located in the `scripts` directory. Try running `make` to show the available commands and tasks. The *commands* do not need the Python dependencies to be installed, while the *tasks* do. The cross-platform tasks are written in Python, thanks to [duty](https://github.com/pawamoy/duty).
+
+If you work in VSCode, we provide [an action to configure VSCode](https://pawamoy.github.io/copier-uv/work/#vscode-setup) for the project.
+
+## Development
+
+As usual:
+
+1. create a new branch: `git switch -c feature-or-bugfix-name`
+1. edit the code and/or the documentation
+
+**Before committing:**
+
+1. run `make format` to auto-format the code
+1. run `make check` to check everything (fix any warning)
+1. run `make test` to run the tests (fix any issue)
+1. if you updated the documentation or the project dependencies:
+    1. run `make docs`
+    1. go to http://localhost:8000 and check that everything looks good
+1. follow our [commit message convention](#commit-message-convention)
+
+If you are unsure about how to fix or ignore a warning, just let the continuous integration fail, and we will help you during review.
+
+Don't bother updating the changelog, we will take care of this.
+
+## Commit message convention
+
+Commit messages must follow our convention based on the [Angular style](https://gist.github.com/stephenparish/9941e89d80e2bc58a153#format-of-the-commit-message) or the [Karma convention](https://karma-runner.github.io/4.0/dev/git-commit-msg.html):
+
+```
+<type>[(scope)]: Subject
+
+[Body]
+```
+
+**Subject and body must be valid Markdown.** Subject must have proper casing (uppercase for first letter if it makes sense), but no dot at the end, and no punctuation in general.
+
+Scope and body are optional. Type can be:
+
+- `build`: About packaging, building wheels, etc.
+- `chore`: About packaging or repo/files management.
+- `ci`: About Continuous Integration.
+- `deps`: Dependencies update.
+- `docs`: About documentation.
+- `feat`: New feature.
+- `fix`: Bug fix.
+- `perf`: About performance.
+- `refactor`: Changes that are not features or bug fixes.
+- `style`: A change in code style/format.
+- `tests`: About tests.
+
+If you write a body, please add trailers at the end (for example issues and PR references, or co-authors), without relying on GitHub's flavored Markdown:
+
+```
+Body.
+
+Issue #10: https://github.com/namespace/project/issues/10
+Related to PR namespace/other-project#15: https://github.com/namespace/other-project/pull/15
+```
+
+These "trailers" must appear at the end of the body, without any blank lines between them. The trailer title can contain any character except colons `:`. We expect a full URI for each trailer, not just GitHub autolinks (for example, full GitHub URLs for commits and issues, not the hash or the #issue-number).
+
+We do not enforce a line length on commit messages summary and body, but please avoid very long summaries, and very long lines in the body, unless they are part of code blocks that must not be wrapped.
+
+## Pull requests guidelines
+
+Link to any related issue in the Pull Request message.
+
+During the review, we recommend using fixups:
+
+```bash
+# SHA is the SHA of the commit you want to fix
+git commit --fixup=SHA
+```
+
+Once all the changes are approved, you can squash your commits:
+
+```bash
+git rebase -i --autosquash main
+```
+
+And force-push:
+
+```bash
+git push -f
+```
+
+If this seems all too complicated, you can push or force-push each new commit, and we will squash them ourselves if needed, before merging.

iseewhatyoudid-0.1.0/LICENSE

@@ -0,0 +1,15 @@
+ISC License
+
+Copyright (c) 2026, Timothée Mazzucotelli and contributors
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

iseewhatyoudid-0.1.0/PKG-INFO

@@ -0,0 +1,309 @@
+Metadata-Version: 2.4
+Name: iseewhatyoudid
+Version: 0.1.0
+Summary: Overview of what you achieved.
+Author-Email: Timothée Mazzucotelli <dev@pawamoy.fr>
+License-Expression: ISC
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Topic :: Documentation
+Classifier: Topic :: Software Development
+Classifier: Topic :: Utilities
+Classifier: Typing :: Typed
+Project-URL: Homepage, https://pawamoy.github.io/iseewhatyoudid
+Project-URL: Documentation, https://pawamoy.github.io/iseewhatyoudid
+Project-URL: Changelog, https://pawamoy.github.io/iseewhatyoudid/changelog
+Project-URL: Repository, https://github.com/pawamoy/iseewhatyoudid
+Project-URL: Issues, https://github.com/pawamoy/iseewhatyoudid/issues
+Project-URL: Discussions, https://github.com/pawamoy/iseewhatyoudid/discussions
+Project-URL: Gitter, https://gitter.im/iseewhatyoudid/community
+Project-URL: Funding, https://github.com/sponsors/pawamoy
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+# iseewhatyoudid
+
+[![ci](https://github.com/pawamoy/iseewhatyoudid/workflows/ci/badge.svg)](https://github.com/pawamoy/iseewhatyoudid/actions?query=workflow%3Aci)
+[![documentation](https://img.shields.io/badge/docs-zensical-FF9100.svg?style=flat)](https://pawamoy.github.io/iseewhatyoudid/)
+[![pypi version](https://img.shields.io/pypi/v/iseewhatyoudid.svg)](https://pypi.org/project/iseewhatyoudid/)
+[![gitter](https://img.shields.io/badge/matrix-chat-4DB798.svg?style=flat)](https://app.gitter.im/#/room/#iseewhatyoudid:gitter.im)
+
+`iseewhatyoudid` is a small reminder that your work adds up. When you are
+feeling as though you have not done enough, it lets you look back over the
+issues and pull requests you have contributed, step by step and over time.
+
+It creates an interactive HTML dashboard of a GitHub user's activity: issues
+and pull requests they opened, status changes on those items, issue and pull
+request comments they wrote, and commit contributions. Activity is grouped by
+year, month, week, and day across every visible repository by default.
+
+## A gentle reminder, not a scorecard
+
+This tool is intentionally a double-edged one. Seeing your past activity can
+help you recognise work that was easy to forget. It can also reinforce a sense
+of being unproductive when activity is low, when GitHub does not capture the
+work you did, or when you are simply going through a quieter period.
+
+Take the dashboard with a grain of salt. GitHub activity does not measure a
+person's worth, pleasure, or happiness—and it is not a complete measure of
+their work or impact. Rest, learning, care, conversations, planning, and work
+away from GitHub all matter too.
+
+## Installation
+
+```bash
+pip install iseewhatyoudid
+```
+
+With [`uv`](https://docs.astral.sh/uv/):
+
+```bash
+uv tool install iseewhatyoudid
+```
+
+Python 3.10 or later is required.
+
+## Usage
+
+By default, the dashboard shows all activity for the GitHub account
+authenticated in `gh`.
+
+```bash
+iseewhatyoudid dashboard
+```
+
+Pass `--user` to inspect a different GitHub user. Repository scopes are
+optional filters: an organization (`--org`) or an individual repository
+(`--include-repo`).
+
+```bash
+iseewhatyoudid dashboard --user octocat --include-repo octo-org/example
+```
+
+To inspect all repositories in an organization:
+
+```bash
+iseewhatyoudid dashboard --user octocat --org octo-org
+```
+
+The command writes `iseewhatyoudid.html` in the current directory. Open it in a
+browser to explore a personal history of how your work accumulated:
+
+- a cumulative chart that only moves forward, with contribution milestones;
+- a one-square-per-day activity tapestry;
+- active-time, repository, conversation, and return-after-a-break insights;
+- issue and pull-request lifecycle views;
+- contribution variety, repository stewardship, and project exploration;
+- personal records, first contributions, and yearly chapter cards;
+- a long-term monthly rhythm; and
+- links that help rediscover older issues and pull requests;
+- commit-summary work types, including features, fixes, documentation, tests,
+  refactoring, security, accessibility, CI, maintenance, and more;
+- commit composition and cumulative work-type charts, a filterable commit
+  heatmap, repository/type matrix, and project-role views;
+- care-work summaries, milestones, maintenance seasons, recurring topics, and
+  conventional-prefix coverage; and
+- a searchable, linked commit-summary gallery plus locally derived personal
+  insights.
+
+The detailed stacked views for years, recent months, weeks, and days remain
+available near the end of the report.
+
+### Authentication
+
+The command uses the [GitHub CLI](https://cli.github.com/) for authentication
+and GraphQL requests. Install `gh` and sign in once before running the
+dashboard. Its browser-based sign-in flow stores the credential in your system
+credential store when one is available.
+
+```bash
+gh auth login
+iseewhatyoudid dashboard --org my-organization
+```
+
+When no `--user` is given, the account authenticated in `gh` is used. Make
+sure that account can access the repositories you include.
+
+### Scoping and filtering
+
+`--org`, `--include-repo`, and `--exclude-repo` can each be repeated. Without
+an organization or included repository, all repositories are included.
+Otherwise, included repositories are combined with organization repositories;
+exclusions always take precedence.
+
+```bash
+# Activity in two organizations, plus one standalone repository.
+iseewhatyoudid dashboard \
+  --user octocat \
+  --org octo-org \
+  --org another-org \
+  --include-repo someone/project \
+  --exclude-repo octo-org/archived-project
+```
+
+Run `iseewhatyoudid dashboard --help` to see every option. While GitHub data
+is loading, the command displays a progress bar with fetched and total page
+counts. Logging is disabled by default. Add `-v` for Rich-formatted API logging,
+`-vv` for debug logging, or use `--log-level` to enable an explicit logging
+level. Add `--refresh` to bypass the short-lived cache when you need the very
+latest data.
+
+### Using local clones for deeper commit history
+
+If your public repositories are already cloned below one or more directories,
+point the dashboard at them with `--repos-dir`:
+
+```bash
+iseewhatyoudid dashboard --repos-dir ~/dev
+```
+
+The option can be repeated. The command recursively discovers Git clones,
+normalizes each `origin` remote that points to `github.com` in the selected
+scope, and asks GitHub for only its canonical repository name, privacy status,
+and default-branch name. Other remotes—such as contributor forks added while
+reviewing pull requests—are ignored. Repositories do not need to appear in
+GitHub's contribution list to qualify.
+Discovery continues into the selected directory when that directory is itself
+a Git repository, so a Git-backed container of nested clones works as expected.
+The command then reads the local default branch without fetching, checking out,
+or changing the clone. Matched local histories replace commit-summary API
+requests; unmatched repositories keep the bounded GitHub fallback.
+
+For the authenticated user, commits match the repository's configured Git
+email, GitHub's `<login>@users.noreply.github.com` forms, and mailmap aliases.
+Add old or additional identities explicitly when needed:
+
+```bash
+iseewhatyoudid dashboard \
+  --repos-dir ~/work \
+  --repos-dir ~/projects \
+  --commit-author-email old-address@example.com
+```
+
+`--commit-author-email` can also be repeated. When `--user` selects another
+person, local Git configuration is deliberately not assumed to belong to that
+person; pass their known author emails explicitly. GitHub noreply addresses
+matching the selected login continue to work automatically.
+
+### HTML dashboard
+
+Use `--output-html` to choose a different destination for the dashboard.
+
+```bash
+iseewhatyoudid dashboard --output-html activity.html
+```
+
+The report uses [Chart.js](https://www.chartjs.org/) from its CDN, so opening
+it requires network access. Hover over bars to inspect values or click legend
+entries to show and hide activity categories. Summary cards show totals and
+yearly/monthly averages, while a GitHub-style grid shows daily activity over
+the last year.
+
+### Cache
+
+Activity is cached in the operating system's user cache directory, as resolved
+by [`platformdirs`](https://platformdirs.readthedocs.io/). After the initial
+history fetch, later runs request only the newest issue, pull request, and
+comment pages, refresh items that are still open or were closed recently, reuse
+completed commit years, and update the current year's commits. Merged pull
+requests and items closed for more than 30 days are treated as stable. Results
+fetched during the last 15 minutes are reused entirely, making quick dashboard
+reruns local-only after the authenticated username has been resolved.
+
+The cache stores only the GitHub IDs, timestamps, states, repository names,
+titles, URLs, numbers, author logins, commit SHAs, and single-line commit
+summaries needed to rebuild the dashboard and its rediscovery links. It does
+not store comment bodies, issue descriptions, multi-line commit messages,
+patches, file contents, credentials, or local filesystem paths. For a matched
+local clone it additionally stores the repository's last inspected commit,
+reference name, shallow status, and a one-way fingerprint of the author
+identities so unchanged histories require no commit scan on the next run.
+
+### Commit-summary collection
+
+Local clones are the preferred source when `--repos-dir` is used. Full clones
+provide up to the newest 2,000 matching commits from the locally available
+default-branch history per repository. Shallow clones provide only the history
+present on disk and are labeled as shallow in the dashboard. New descendants
+are scanned incrementally from the previously cached head. Rewritten histories
+and changed author identities are rescanned; unchanged shallow clones are
+reused, while deepened clones are detected and rescanned. Commit records remain
+cached by immutable SHA, and older records are trimmed when a repository
+exceeds the 2,000-commit limit.
+
+For repositories without a usable local clone, commit-summary analysis is
+deliberately bounded so it does not turn dashboard generation into a remote
+repository crawl. Within the selected dashboard scope, the collector ranks
+public repositories using the contribution counts already available and
+samples at most 20 repositories. Repositories are batched ten at a time in
+GraphQL requests. The first import retrieves only the newest 100 default-branch
+commits attributed to the selected GitHub user in each sampled repository.
+
+Commits are cached by immutable SHA. A normal refresh requests the newest page
+and stops as soon as it sees a cached SHA. If more than a full page of new
+commits appeared since the previous run, it can follow at most three pages per
+repository. The dashboard reports how many histories came from local clones,
+how many were shallow, and how many used the bounded GitHub sample.
+
+The classifier recognizes forgiving Conventional Commit-style prefixes such
+as `feat`, `feature`, `fix`, `docs`, `test`, `tests`, `refactor`, `perf`,
+`security`, `a11y`, `i18n`, `deps`, `ci`, `build`, `chore`, and `revert`, with
+optional scopes such as `feat(parser): ...`. Unrecognized summaries stay in a
+normal “Other” category; they are not treated as malformed.
+
+Default merge subjects such as `Merge branch ...` and
+`Merge pull request ...` are excluded from commit-summary analysis so routine
+integration commits do not dominate work types or recurring themes. Custom
+merge commit subjects remain part of the analysis.
+
+Private repositories are excluded from the cache and dashboard. GitHub's
+complete user-wide issue, pull-request, and comment connections do not support
+a public-only filter, so an authenticated response can transiently contain
+private nodes. The collector checks each repository's `isPrivate` flag and
+discards those nodes before adding anything to its history maps or writing a
+cache checkpoint. Private commit-contribution groups are discarded in the same
+way. Older cache schemas are invalidated and overwritten before collection
+starts.
+
+## Current limitations
+
+Closed and merged dates describe status changes on issues and pull requests
+authored by the selected user; GitHub does not expose a global stream of items
+that the user personally closed or merged. Comments include issue comments and
+top-level pull-request conversation comments, but not inline review comments.
+
+GitHub's contribution API returns commit activity from at most 100 repositories
+per year. For unusually active single repositories, the dashboard combines the
+first and last 100 commit-days returned by GitHub and warns when the API still
+truncates the year.
+
+Commit-summary analysis covers only public default branches. Local clones can
+be stale until they are updated outside this program, and shallow clones omit
+history that is absent from disk. The GitHub fallback can omit older commits
+beyond its initial sample. Both sources omit unmerged branch commits and
+commits no longer reachable after rebases or force-pushes. Commits whose author
+email does not match a configured identity can also be absent, and squashed
+commits may not correspond one-to-one with the user's original commits.
+
+## Troubleshooting
+
+- Install [GitHub CLI](https://cli.github.com/) and run `gh auth login` before
+  using the dashboard.
+- Check repository names use the `owner/name` form.
+- If GitHub returns a rate-limit or permission error, check `gh auth status`
+  and make sure the authenticated account can access the selected repositories.
+- Run `iseewhatyoudid --debug-info` when reporting an environment issue.
+
+## Sponsors
+
+<!-- sponsors-start -->
+<!-- sponsors-end -->