Weekly status pages written from public repository activity, not from meetings.
All status pages · Unowned issues across all projects · How to write a weekly status report from GitHub
2026-10-14 to 2026-10-20 (7 full days, UTC). Unofficial: generated from this repository’s public GitHub activity by pilotless status. Not affiliated with the project, and no information here that GitHub does not publish.
16 commits to main by 8 people, 16 pull requests merged, 57 open pull requests, 35 open issues on this page of results.
Open, and untouched for seven days or more:
[popover] - last touched 287 days agoOpen, unassigned, and with no replies yet:
core.excludesFile, so globally-ignored directories are scanned - opened 28 days agoengines.node from >= 20 to >= 10 (N-API 3 runtime compatibility) - opened 37 days agovariant="outline" to "outline-solid" inside conditional expre - opened 54 days agoThe two lists above are what a status meeting is usually for. Nobody had to attend one to produce this page.
If you maintain tailwindlabs/tailwindcss and would rather this page did not exist, open an issue and it will be deleted - no argument, no reply needed beyond the repository name.
Want this for your own repositories? Install the pilotless GitHub App — one click, then a pinned weekly status digest in each selected repo. Prefer CI-only? The status-action is still two lines of YAML with no account and nothing leaving GitHub.