Skip to content

Update README.md - #1

Merged
aidanbebbington merged 1 commit into
twcclegg:masterfrom
weitzhandler:patch-1
Aug 6, 2016
Merged

Update README.md#1
aidanbebbington merged 1 commit into
twcclegg:masterfrom
weitzhandler:patch-1

Conversation

@weitzhandler

Copy link
Copy Markdown
Contributor

Updated NuGet package and formatted links.

@aidanbebbington
aidanbebbington merged commit 802e7f6 into twcclegg:master Aug 6, 2016
@aidanbebbington

Copy link
Copy Markdown
Collaborator

thanks :)

twcclegg pushed a commit that referenced this pull request Aug 26, 2026
Every issue from #1 through #422 is now either a PR, a listed metadata
issue, or implicitly a non-metadata issue by not appearing in the list -
there's no separate "not metadata" file anymore. Went back through the
full closed-issue history (including several titles that didn't obviously
scream "metadata" but turned out to be, like #14, #25, #109, #149, #165,
#181, and #91) to make the positive list genuinely exhaustive rather than
a curated sample, taking it from 30 to 39 entries.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WVGRJyQwtvBGXAmWswxyqW
twcclegg pushed a commit that referenced this pull request Aug 26, 2026
A large fraction of issues filed here are reports about upstream Google
libphonenumber metadata (unrecognized prefixes, outdated numbering plans)
rather than bugs in this C# port's code, and maintainers have been closing
these by hand with a pointer to google/libphonenumber for years. Add a
GitHub Actions workflow that runs the GitHub Copilot CLI against each new
issue to classify it, and when confident it's a metadata report, labels it,
posts a canned comment redirecting to upstream, and closes it - noting the
closure was automatic and inviting a reopen if it's a false positive.

The classifier is grounded in .github/triage/metadata_examples.md, an
exhaustive, human-verified list of every metadata issue in this repo's
history (#1 through #422): every issue in that range is either a PR, a
listed metadata issue, or - by not appearing in the list - implicitly a
non-metadata issue, with no separate negative list needed. Every time the
workflow closes a new issue as a metadata issue, it opens a PR appending it
to that file, so the classifier's grounding keeps growing from real,
maintainer-confirmed outcomes.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WVGRJyQwtvBGXAmWswxyqW
twcclegg added a commit that referenced this pull request Aug 26, 2026
"Every issue from #1 through #422" would need updating every time the
issue counter moves. State what the list is without pinning it to a
number that's already stale by the time this merges.
twcclegg added a commit that referenced this pull request Aug 26, 2026
Same fix as f03c3d1 for metadata_examples.md - "#1 through #422"
goes stale the moment the issue counter moves past it.
twcclegg added a commit that referenced this pull request Aug 26, 2026
Same fix as f03c3d1/d27cd897 - the automated-triage section had the
same "#1 through #422 at time of writing" pattern.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants