build: update org name from github to github-community-projects (#485)

* build: update org name from github to github-community-projects

Replace all instances of github/evergreen with
github-community-projects/evergreen to reflect the repository
transfer. Update Docker image references, bump version to v2,
update CODEOWNERS, and add transfer notice to README.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Update pull request template by removing checklist items

Removed checklist items related to data publishing and reviewer labeling.

Signed-off-by: Zack Koppert <zkoppert@github.com>

* chore: Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Jason Meridth <jmeridth@gmail.com>

* fix: lint of README via prettier

Signed-off-by: jmeridth <jmeridth@gmail.com>

---------

Signed-off-by: Zack Koppert <zkoppert@github.com>
Signed-off-by: Jason Meridth <jmeridth@gmail.com>
Signed-off-by: jmeridth <jmeridth@gmail.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Jason Meridth <jmeridth@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: 4 people

.github/CODEOWNERS

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

.github/ISSUE_TEMPLATE/config.yml

@@ -2,7 +2,7 @@ blank_issues_enabled: false
 
 contact_links:
   - name: Ask a question
-    url: https://github.com/github/evergreen/discussions/new
+    url: https://github.com/github-community-projects/evergreen/discussions/new
     about: Ask a question or start a discussion
   - name: GitHub OSPO GitHub Action Overall Issue
     url: https://github.com/github/github-ospo/issues/new

.github/pull_request_template.md

@@ -20,8 +20,3 @@ examples: "feat: add new logger" or "fix: remove unused imports"
 - [ ] If documentation is needed for this change, has that been included in this pull request
 - [ ] run `make lint` and fix any issues that you have introduced
 - [ ] run `make test` and ensure you have test coverage for the lines you are introducing
-- [ ] If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from `@jeffrey-luszcz`
-
-### Reviewer
-
-- [ ] Label as either `fix`, `documentation`, `enhancement`, `infrastructure`, `maintenance` or `breaking`

.github/workflows/contributors_report.yaml

@@ -34,7 +34,7 @@ jobs:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           START_DATE: ${{ env.START_DATE }}
           END_DATE: ${{ env.END_DATE }}
-          REPOSITORY: github/evergreen
+          REPOSITORY: github-community-projects/evergreen
           SPONSOR_INFO: "true"
 
       - name: Create issue

CONTRIBUTING.md

@@ -19,11 +19,11 @@ All types of contributions are encouraged and valued. See the [Table of Contents
 
 ## I Have a Question
 
-Before you ask a question, it is best to search for existing [Issues](https://github.com/github/evergreen/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue.
+Before you ask a question, it is best to search for existing [Issues](https://github.com/github-community-projects/evergreen/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue.
 
 If you then still feel the need to ask a question and need clarification, we recommend the following:
 
-- Open an [Issue](https://github.com/github/evergreen/issues/new).
+- Open an [Issue](https://github.com/github-community-projects/evergreen/issues/new).
 - Provide as much context as you can about what you're running into.
 - Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
 
@@ -45,7 +45,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 - Make sure that you are using the latest version.
 - Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the documentation. If you are looking for support, you might want to check [this section](#i-have-a-question)).
-- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/github/evergreen/issues).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/github-community-projects/evergreen/issues).
 - Collect information about the bug:
   - Stack trace (Traceback)
   - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
@@ -57,7 +57,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 
 ### How Do I Submit a Good Bug Report?
 
-Please submit a bug report using our [GitHub Issues template](https://github.com/github/evergreen/issues/new?template=bug_report.yml).
+Please submit a bug report using our [GitHub Issues template](https://github.com/github-community-projects/evergreen/issues/new?template=bug_report.yml).
 
 ## Suggesting Enhancements
 
@@ -69,14 +69,14 @@ This section guides you through submitting an enhancement suggestion for evergre
 
 - Make sure that you are using the latest version.
 - Read the documentation carefully and find out if the functionality is already covered, maybe by an individual configuration.
-- Perform a [search](https://github.com/github/evergreen/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Perform a [search](https://github.com/github-community-projects/evergreen/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature or to develop the feature yourself and contribute it to the project.
 
 <!-- omit in toc -->
 
 ### How Do I Submit a Good Enhancement Suggestion?
 
-Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github/evergreen/issues/new?template=feature_request.yml).
+Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github-community-projects/evergreen/issues/new?template=feature_request.yml).
 
 ### Pull Request Standards
 
@@ -86,4 +86,4 @@ We are using [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.
 
 Releases are automated if a pull request is labelled with our [SemVer related labels](.github/release-drafter.yml) or with the `vuln` or `release` labels.
 
-You can also manually initiate a release you can do so through the GitHub Actions UI. If you have permissions to do so, you can navigate to the [Actions tab](https://github.com/github/evergreen/actions/workflows/release.yml) and select the `Run workflow` button. This will allow you to select the branch to release from and the version to release.
+You can also manually initiate a release through the GitHub Actions UI. If you have permissions to do so, you can navigate to the [Actions tab](https://github.com/github-community-projects/evergreen/actions/workflows/release.yml) and select the `Run workflow` button. This will allow you to select the branch to release from and the version to release.

Dockerfile

@@ -2,7 +2,7 @@
 #checkov:skip=CKV_DOCKER_3
 #trivy:ignore:AVD-DS-0002
 FROM python:3.14.0-slim@sha256:0aecac02dc3d4c5dbb024b753af084cafe41f5416e02193f1ce345d671ec966e
-LABEL org.opencontainers.image.source https://github.com/github/evergreen
+LABEL org.opencontainers.image.source https://github.com/github-community-projects/evergreen
 
 WORKDIR /action/workspace
 COPY requirements.txt *.py /action/workspace/