treewide: update repository references to meta/bpfilter

.github/workflows/claude-pr-review.yaml

@@ -21,7 +21,7 @@ jobs:
     setup:
         runs-on: ubuntu-latest
         if: |
-          github.repository_owner == 'facebook' &&
+          github.repository_owner == 'meta' &&
           ((github.event_name == 'pull_request_target' &&
             github.event.pull_request.base.ref == 'main' &&
             contains(fromJSON('["MEMBER","OWNER","COLLABORATOR"]'), github.event.pull_request.author_association))) ||
@@ -112,7 +112,7 @@ jobs:
               uses: aws-actions/configure-aws-credentials@8df5847569e6427dd6c4fb1cf565c83acfa8afa7
               with:
                   role-to-assume: arn:aws:iam::${{ secrets.AWS_ACCOUNT_ID }}:role/${{ secrets.AWS_ROLE_NAME }}
-                  role-session-name: GitHubActions-facebook-bpfilter-${{ github.run_id }}
+                  role-session-name: GitHubActions-meta-bpfilter-${{ github.run_id }}
                   aws-region: us-east-1
 
             - name: Run Claude Code

doc/_static/benchmarks.html

@@ -184,7 +184,7 @@
                         const sha = e.chart.tooltip.dataPoints[0].label
                         if (sha.endsWith("+"))
                             return;
-                        window.open("https://github.com/facebook/bpfilter/commit/" + sha, "_blank");
+                        window.open("https://github.com/meta/bpfilter/commit/" + sha, "_blank");
                     }
                 }
             });

doc/developers/contributing.rst

@@ -24,14 +24,14 @@ So before you open a PR:
 
 We close PRs, without a full review, when they were clearly never read by their author, weren't tested, or ignore the style guide after a heads-up. If it keeps happening we'll block you. We've spent more time on some of these review comments than the author spent opening the PR, and we won't keep making that trade.
 
-If you're new and willing to put the work in, you're welcome here and we'll take the time to ramp you up. Pick something tagged `good first issue <https://github.com/facebook/bpfilter/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22>`_, or email us (qde@naccy.de) and we'll find you a good starting task.
+If you're new and willing to put the work in, you're welcome here and we'll take the time to ramp you up. Pick something tagged `good first issue <https://github.com/meta/bpfilter/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22>`_, or email us (qde@naccy.de) and we'll find you a good starting task.
 
 Where to start
 --------------
 
 If you want to start contributing to bpfilter, the best way to get to know the codebase would be to start with one of the ``@todo`` available in the code. Most of those tasks are small, self-contained, work trivial enough that they do not deserve their GitHub issue.
 
-Once you know your way around the structure of the project, feel free to continue with the ``@todo``, or jump on a bigger issue in the `GitHub issues tracker <https://github.com/facebook/bpfilter/issues>`_.
+Once you know your way around the structure of the project, feel free to continue with the ``@todo``, or jump on a bigger issue in the `GitHub issues tracker <https://github.com/meta/bpfilter/issues>`_.
 
 Join the `bpfilter Slack workspace <https://join.slack.com/t/bpfilter/shared_invite/zt-4d89whuae-JnJJ~h0zpdHwzP7wyYQpwA>`_ to ask questions or discuss contributions. You can also email qde@naccy.de.
 

doc/index.rst

@@ -28,7 +28,7 @@
    :hidden:
    :caption: External
 
-   GitHub repository <https://github.com/facebook/bpfilter>
+   GitHub repository <https://github.com/meta/bpfilter>
    Slack community <https://join.slack.com/t/bpfilter/shared_invite/zt-4d89whuae-JnJJ~h0zpdHwzP7wyYQpwA>
    external/benchmarks/index
    external/coverage/index

src/libbpfilter/bpfilter.pc.in

@@ -4,7 +4,7 @@ libdir=${prefix}/@CMAKE_INSTALL_LIBDIR@
 
 Name: bpfilter
 Description: BPF-based packet filtering framework
-URL: https://github.com/facebook/bpfilter
+URL: https://github.com/meta/bpfilter
 Version: @PROJECT_VERSION@@PROJECT_VERSION_SUFFIX@
 Cflags: -I${includedir}
 Libs: -L${libdir} -lbpfilter

tests/benchmarks/results.html.j2

@@ -680,7 +680,7 @@
                     onClick: function(event, elements) {
                         if (elements.length > 0 && fullCommits) {
                             const sha = fullCommits[elements[0].index];
-                            window.open(`https://github.com/facebook/bpfilter/commit/${sha}`, '_blank');
+                            window.open(`https://github.com/meta/bpfilter/commit/${sha}`, '_blank');
                         }
                     },
                     scales: {

tests/e2e/matchers/meta_probability.cpp

@@ -26,7 +26,7 @@ extern "C" {
  * approximation that is a false failure probability of about 2e-9 per case;
  * the exact binomial tail is larger for the rare-event case (about 2e-8 for
  * 99.9%), so the suite-wide risk over all hooks and cases stays in the 1e-7
- * range. The regression this guards against (facebook/bpfilter#583: every
+ * range. The regression this guards against (meta/bpfilter#583: every
  * probability above 50% behaving like 100%, and like 0% when negated) is 25+
  * points away at 75%.
  */
@@ -96,7 +96,7 @@ static void _bft_assert_probability_rate(MatcherTest *test, float proba,
 
 /**
  * Verify meta.probability matches at the configured rate on both sides of the
- * 50% boundary, where the threshold crosses INT32_MAX (facebook/bpfilter#583).
+ * 50% boundary, where the threshold crosses INT32_MAX (meta/bpfilter#583).
  */
 static void _bft_meta_probability_eq_rate(MatcherTest *test)
 {