chore(ci): handle renames after move to GitHub org

.github/CODEOWNERS

@@ -1 +1 @@
-* @jmeridth
+* @github/ospo-github-actions

.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

.github/workflows/test-pr-title.yaml

@@ -30,6 +30,6 @@ jobs:
       scopes: |
         ci
         docs
-      requireScope: true
+      requireScope: false
     secrets:
       github-token: ${{ secrets.GITHUB_TOKEN }}

.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:

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

README.md

@@ -13,16 +13,15 @@ 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:
 >
 > - [labeler.yml](.github/labeler.yml)
 > - [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.

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.
 

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

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

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

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

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

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