From 39143a1f10a1699883cbc32f8c99a97d56f21d66 Mon Sep 17 00:00:00 2001 From: Axiom Bot <0xAxiom@users.noreply.github.com> Date: Mon, 18 May 2026 23:24:23 -0700 Subject: [PATCH] docs: update stale base-org references to base org in README The GitHub org moved from `base-org` to `base`. The README still referenced the old org in the contract-deployments link and in all shields.io badge image URLs (contributors, commit-activity, stars, repo-size, license, issues-pr, issues-raw). Badge link targets were already correct; only the image URLs and the contract-deployments prose link remained stale. Fixes #248 --- README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 9f9ae270..1b45f93e 100644 --- a/README.md +++ b/README.md @@ -4,15 +4,15 @@ This repo contains contracts and scripts for Base. Note that Base primarily utilizes Optimism's bedrock contracts located in Optimism's repo [here](https://github.com/ethereum-optimism/optimism/tree/develop/packages/contracts-bedrock). -For contract deployment artifacts, see [base-org/contract-deployments](https://github.com/base-org/contract-deployments). +For contract deployment artifacts, see [base/contract-deployments](https://github.com/base/contract-deployments). -[![GitHub contributors](https://img.shields.io/github/contributors/base-org/contracts)](https://github.com/base/contracts/graphs/contributors) -[![GitHub commit activity](https://img.shields.io/github/commit-activity/w/base-org/contracts)](https://github.com/base/contracts/graphs/contributors) -[![GitHub Stars](https://img.shields.io/github/stars/base-org/contracts.svg)](https://github.com/base/contracts/stargazers) -![GitHub repo size](https://img.shields.io/github/repo-size/base-org/contracts) -[![GitHub](https://img.shields.io/github/license/base-org/contracts?color=blue)](https://github.com/base/contracts/blob/main/LICENSE) +[![GitHub contributors](https://img.shields.io/github/contributors/base/contracts)](https://github.com/base/contracts/graphs/contributors) +[![GitHub commit activity](https://img.shields.io/github/commit-activity/w/base/contracts)](https://github.com/base/contracts/graphs/contributors) +[![GitHub Stars](https://img.shields.io/github/stars/base/contracts.svg)](https://github.com/base/contracts/stargazers) +![GitHub repo size](https://img.shields.io/github/repo-size/base/contracts) +[![GitHub](https://img.shields.io/github/license/base/contracts?color=blue)](https://github.com/base/contracts/blob/main/LICENSE) @@ -24,8 +24,8 @@ For contract deployment artifacts, see [base-org/contract-deployments](https://g -[![GitHub pull requests by-label](https://img.shields.io/github/issues-pr-raw/base-org/contracts)](https://github.com/base/contracts/pulls) -[![GitHub Issues](https://img.shields.io/github/issues-raw/base-org/contracts.svg)](https://github.com/base/contracts/issues) +[![GitHub pull requests by-label](https://img.shields.io/github/issues-pr-raw/base/contracts)](https://github.com/base/contracts/pulls) +[![GitHub Issues](https://img.shields.io/github/issues-raw/base/contracts.svg)](https://github.com/base/contracts/issues) ### Fixing semver-lock CI failures