[GH-ISSUE #3448] [Workflow] Introduce a dedicated .github repository for centralized community health files and reusable workflows #1293

New issue

Open

opened 2026-10-16 21:03:50 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-16 21:03:50 +00:00

Owner

Originally created by @matbrgz on GitHub (Oct 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/3448

Before submitting

I searched the open and closed issues and pull requests for a related discussion.
I understand the contribution scope must be reviewed before integration; open questions are welcome here.
This discussion does not include credentials, private samples, or sensitive target data.

Decision needed

Would maintainers consider adopting a dedicated .github repository (and optionally .github-private for internal/security automation) to centralize organization-wide community health files, issue/PR templates, and reusable GitHub Actions workflows?

Context and evidence

As REA's project footprint expands across multiple repositories (such as the core codebase, documentation/website assets, separate skills packages, and potential future bridge sub-repos):

Maintaining duplicate .github/ directories (templates, security policies, codes of conduct, and CI workflows) across multiple repositories leads to drift and increased maintenance overhead.
GitHub provides a native pattern for organizations: a special repository named .github (e.g. rea-tools/.github). Any repository in the organization that does not have its own specific health files automatically inherits them from this central repository:
1. Default .github/CODEOWNERS
2. Standardized Issue Forms (.github/ISSUE_TEMPLATE/) and Pull Request templates (.github/pull_request_template.md)
3. Global SECURITY.md, CONTRIBUTING.md, and CODE_OF_CONDUCT.md
4. Organization showcase and landing page (profile/README.md)
5. Shared, reusable GitHub Actions workflows (.github/workflows/*.yml via workflow_call) to avoid copying complex CI verification definitions across repositories.

Furthermore, for security and vulnerability disclosure triage, organizations often employ a complementary .github-private repository to coordinate confidential verification harnesses and private reusable workflows before public release.

Expected interaction with targets

No target interaction (documentation or usability only)

Options and tradeoffs

Option A (.github repository for org-wide defaults): Create a .github repository to host fallback community health files, organization profile documentation, and reusable CI workflows across all project repositories.
Option B (Repository-local files only): Continue keeping all .github/ definitions isolated within individual repositories.

Verification readiness

Idea only; I need help defining checks

References

GitHub Documentation on Creating a default community health file for your organization
GitHub Documentation on Reusing workflows
Related governance discussion: #3447

Originally created by @matbrgz on GitHub (Oct 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/3448 [![Type: Feature](https://img.shields.io/badge/type-feature-blue.svg?style=flat-square)](https://github.com/morluto/rea) [![Domain: Game & Engine RE](https://img.shields.io/badge/domain-game_&_engine_RE-green.svg?style=flat-square)](https://github.com/morluto/rea) [![Status: Proposed](https://img.shields.io/badge/status-proposed-blue.svg?style=flat-square)](https://github.com/morluto/rea) [![Ecosystem: REA](https://img.shields.io/badge/ecosystem-morluto%2Frea-8A2BE2.svg?style=flat-square)](https://github.com/morluto/rea) ### Before submitting - [x] I searched the open and closed issues and pull requests for a related discussion. - [x] I understand the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope) must be reviewed before integration; open questions are welcome here. - [x] This discussion does not include credentials, private samples, or sensitive target data. ### Decision needed Would maintainers consider adopting a dedicated `.github` repository (and optionally `.github-private` for internal/security automation) to centralize organization-wide community health files, issue/PR templates, and reusable GitHub Actions workflows? ### Context and evidence As REA's project footprint expands across multiple repositories (such as the core codebase, documentation/website assets, separate skills packages, and potential future bridge sub-repos): - Maintaining duplicate `.github/` directories (templates, security policies, codes of conduct, and CI workflows) across multiple repositories leads to drift and increased maintenance overhead. - GitHub provides a native pattern for organizations: a special repository named `.github` (e.g. `rea-tools/.github`). Any repository in the organization that does not have its own specific health files automatically inherits them from this central repository: 1. Default `.github/CODEOWNERS` 2. Standardized Issue Forms (`.github/ISSUE_TEMPLATE/`) and Pull Request templates (`.github/pull_request_template.md`) 3. Global `SECURITY.md`, `CONTRIBUTING.md`, and `CODE_OF_CONDUCT.md` 4. Organization showcase and landing page (`profile/README.md`) 5. Shared, reusable GitHub Actions workflows (`.github/workflows/*.yml` via `workflow_call`) to avoid copying complex CI verification definitions across repositories. Furthermore, for security and vulnerability disclosure triage, organizations often employ a complementary `.github-private` repository to coordinate confidential verification harnesses and private reusable workflows before public release. ### Expected interaction with targets - No target interaction (documentation or usability only) ### Options and tradeoffs - **Option A (.github repository for org-wide defaults)**: Create a `.github` repository to host fallback community health files, organization profile documentation, and reusable CI workflows across all project repositories. - **Option B (Repository-local files only)**: Continue keeping all `.github/` definitions isolated within individual repositories. ### Verification readiness - Idea only; I need help defining checks ### References - GitHub Documentation on [Creating a default community health file for your organization](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file) - GitHub Documentation on [Reusing workflows](https://docs.github.com/en/actions/sharing-automations/reusing-workflows) - Related governance discussion: #3447

bsakaguchi referenced this issue

2026-10-17 21:10:04 +00:00

[PR #1293] [MERGED] fix(process): validate terminal byte totals against retained frames #2773

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#1293

No description provided.

Rows
Columns