diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 445e172..a506e1e 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -1 +1 @@
-* @jmeridth
+* @github/ospo-github-actions
diff --git a/.github/ISSUE_TEMPLATE/config.yaml b/.github/ISSUE_TEMPLATE/config.yaml
index d50f113..b3da8d2 100644
--- a/.github/ISSUE_TEMPLATE/config.yaml
+++ b/.github/ISSUE_TEMPLATE/config.yaml
@@ -2,5 +2,5 @@ blank_issues_enabled: false
 
 contact_links:
   - name: Ask a question
-    url: https://github.com/jmeridth/reusable-workflows/discussions/new?category=q-a
+    url: https://github.com/github/ospo-reusable-workflows/discussions/new?category=q-a
     about: Ask a question or start a discussion
diff --git a/.github/workflows/test-pr-title.yaml b/.github/workflows/test-pr-title.yaml
index 8c5ce42..f7d9517 100644
--- a/.github/workflows/test-pr-title.yaml
+++ b/.github/workflows/test-pr-title.yaml
@@ -30,6 +30,6 @@ jobs:
       scopes: |
         ci
         docs
-      requireScope: true
+      requireScope: false
     secrets:
       github-token: ${{ secrets.GITHUB_TOKEN }}
diff --git a/.github/workflows/test-release.yaml b/.github/workflows/test-release.yaml
index 684addb..e9fa18c 100644
--- a/.github/workflows/test-release.yaml
+++ b/.github/workflows/test-release.yaml
@@ -26,7 +26,7 @@ jobs:
       pull-requests: read
     uses: ./.github/workflows/release-image.yaml
     with:
-      image-name: jmeridth/reusable-workflows
+      image-name: github/ospo-reusable-workflows
       full-tag: ${{ needs.release.outputs.full-tag }}
       short-tag: ${{ needs.release.outputs.short-tag }}
     secrets:
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
deleted file mode 100644
index a08311e..0000000
--- a/CODE_OF_CONDUCT.md
+++ /dev/null
@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-- The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers 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, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at <opensource@github.com>. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
diff --git a/LICENSE b/LICENSE
index a3ba75a..2de6c12 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 Jason Meridth
+Copyright (c) GitHub
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
diff --git a/README.md b/README.md
index cc495b3..6d8dd44 100644
--- a/README.md
+++ b/README.md
@@ -13,11 +13,10 @@ This is a placeholder repo for multiple GitHub Actions I use in my personal and
 
 > [!CAUTION]
 > Check the permissions in each reusable workflow to ensure the GitHub token you pass from your calling workflow meets the required permissions. Most of the time just passing `${{ secrets.GITHUB_TOKEN }}` is sufficient.
-> This may require you to go to your repository settings and then Actions to `Actions Permission` and enable reusable workflows.  You may also need to update `Workflow Permissions` to `Read and write permissions`.
+> This may require you to go to your repository settings and then Actions to `Actions Permission` and enable reusable workflows. You may also need to update `Workflow Permissions` to `Read and write permissions`.
 >
 > [Workflows](.github/workflows)
 
-
 > [!TIP]
 > You can reuse the following files in this repository in your own as they are used by the reusable workflows:
 >
@@ -25,4 +24,4 @@ This is a placeholder repo for multiple GitHub Actions I use in my personal and
 > - [release-drafter.yaml](.github/release-drafter.yaml)
 
 > [!WARNING]  
-> The container image generated in this repo is a placeholder, it contains no content. It uses [alpine:latest and says "Hello World"](https://github.com/jmeridth/reusable-workflows/blob/main/Dockerfile).  The image creation option is for GitHub Actions who need it because their Action is not written in JavaScript/Typescript and they want to track downloads/usage.
+> The container image generated in this repo is a placeholder, it contains no content. It uses [alpine:latest and says "Hello World"](https://github.com/github/ospo-reusable-workflows/blob/main/Dockerfile). The image creation option is for GitHub Actions who need it because their Action is not written in JavaScript/Typescript and they want to track downloads/usage.
diff --git a/SECURITY.md b/SECURITY.md
deleted file mode 100644
index ef183e6..0000000
--- a/SECURITY.md
+++ /dev/null
@@ -1,31 +0,0 @@
-Thanks for helping make GitHub safe for everyone.
-
-# Security
-
-GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub).
-
-Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation.
-
-## Reporting Security Issues
-
-If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
-
-**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
-
-Instead, please send an email to opensource-security[@]github.com.
-
-Please include as much of the information listed below as you can to help us better understand and resolve the issue:
-
-- The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
-- Full paths of source file(s) related to the manifestation of the issue
-- The location of the affected source code (tag/branch/commit or direct URL)
-- Any special configuration required to reproduce the issue
-- Step-by-step instructions to reproduce the issue
-- Proof-of-concept or exploit code (if possible)
-- Impact of the issue, including how an attacker might exploit the issue
-
-This information will help us triage your report more quickly.
-
-## Policy
-
-See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms)
diff --git a/SUPPORT.md b/SUPPORT.md
index 68b6078..fccc9c6 100644
--- a/SUPPORT.md
+++ b/SUPPORT.md
@@ -4,7 +4,7 @@
 
 This project uses GitHub issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
 
-For help or questions about using this project, please file a new [Q&A Discussion](https://github.com/jmeridth/reusable-workflows/discussions/new?category=q-a).
+For help or questions about using this project, please file a new [Q&A Discussion](https://github.com/github/ospo-reusable-workflows/discussions/new?category=q-a).
 
 Reusable Workflows is under active development and maintained by GitHub staff and community. We will do our best to respond to support, feature requests, and community questions in a timely manner.
 
diff --git a/docs/auto-labeler.md b/docs/auto-labeler.md
index 4dbab58..6b148ca 100644
--- a/docs/auto-labeler.md
+++ b/docs/auto-labeler.md
@@ -3,7 +3,7 @@
 ## Inputs
 
 ```yaml
-- uses: jmeridth/reusable-workflows/.github/workflows/auto-labeler.yml@main
+- uses: github/ospo-reusable-workflows/.github/workflows/auto-labeler.yml@main
   with:
     # The name of the configuration file to use, default is release-drafter.yml
     # from the release-drafter/release-drafter GitHub Action
diff --git a/docs/labeler.md b/docs/labeler.md
index cdc0e32..ffed2a6 100644
--- a/docs/labeler.md
+++ b/docs/labeler.md
@@ -3,7 +3,7 @@
 ## Inputs
 
 ```yaml
-- uses: jmeridth/reusable-workflows/.github/workflows/labeler.yml@main
+- uses: github/ospo-reusable-workflows/.github/workflows/labeler.yml@main
   with:
     # The name of the configuration file to use, default is labeler.yml
     # from the actions/labeler GitHub Action
diff --git a/docs/pr-title.md b/docs/pr-title.md
index 7282f99..2f9d4cc 100644
--- a/docs/pr-title.md
+++ b/docs/pr-title.md
@@ -3,7 +3,7 @@
 ## Inputs
 
 ```yaml
-- uses: jmeridth/reusable-workflows/.github/workflows/pr-title.yml@main
+- uses: github/ospo-reusable-workflows/.github/workflows/pr-title.yml@main
   with:
     # Configure which types are allowed (newline-delimited).
     # From: https://github.com/commitizen/conventional-commit-types/blob/master/index.json
diff --git a/docs/release-discussion.md b/docs/release-discussion.md
index 6be8a62..b06db7a 100644
--- a/docs/release-discussion.md
+++ b/docs/release-discussion.md
@@ -3,7 +3,7 @@
 ## Inputs
 
 ```yaml
-- uses: jmeridth/reusable-workflows/.github/workflows/release.yml@main
+- uses: github/ospo-reusable-workflows/.github/workflows/release.yml@main
   with:
     # Full tag of the image, usually the version (v1.0.0)
     full-tag: v1.0.0
diff --git a/docs/release-image.md b/docs/release-image.md
index 2cdd4ec..bd47e12 100644
--- a/docs/release-image.md
+++ b/docs/release-image.md
@@ -3,9 +3,9 @@
 ## Inputs
 
 ```yaml
-- uses: jmeridth/reusable-workflows/.github/workflows/release.yml@main
+- uses: github/ospo-reusable-workflows/.github/workflows/release.yml@main
   with:
-    # Image name, usually owner/repository (jmeridth/reusable-workflows)
+    # Image name, usually owner/repository (github/ospo-reusable-workflows)
     image-name: ${{ github.repository }}
     # Full tag of the image, usually the version (v1.0.0)
     full-tag: v1.0.0
diff --git a/docs/release.md b/docs/release.md
index 7f052ab..3be15c9 100644
--- a/docs/release.md
+++ b/docs/release.md
@@ -3,7 +3,7 @@
 ## Inputs
 
 ```yaml
-- uses: jmeridth/reusable-workflows/.github/workflows/release.yml@main
+- uses: github/ospo-reusable-workflows/.github/workflows/release.yml@main
   with:
     # Boolean flag whether to publish the release, default is true
     publish: true