Org profile (README rendered on org page) + shared workflow templates

Go to file

devops-engineer 789adcbbbd Merge pull request 'fix(post-suspension): migrate github.com/Molecule-AI refs to git.moleculesai.app (Class G #168 )' (#4 ) from fix/post-suspension-github-urls into main		2026-05-07 20:04:11 +00:00
profile	fix(post-suspension): migrate github.com/Molecule-AI refs to git.moleculesai.app (Class G #168 )	2026-05-07 13:02:35 -07:00
CONTRIBUTING.md	docs(contributing): add org-wide CONTRIBUTING.md — Gitea-canonical SCM, branch+PR+merge-commit, no force-push to main	2026-05-06 18:38:51 -07:00
README.md	docs(profile): add org-profile README + branding assets, document layout convention	2026-05-06 17:10:56 -07:00
SECURITY.md	docs(security): add org-wide SECURITY.md — security@moleculesai.app, 48h ack, 90d coordinated disclosure	2026-05-06 18:40:13 -07:00

README.md

`Molecule-AI/.github`

Org-level community files + the org-profile README rendered on the org page.

Layout

.github/
├── README.md            # this file (repo entry point, not user-visible on the org page)
└── profile/
    ├── README.md        # rendered on github.com/Molecule-AI when GitHub access is restored
    └── assets/
        ├── molecule-icon.svg
        └── molecule-logo.svg

Convention

GitHub renders <org>/.github/profile/README.md as the org's public landing page. We mirror the same path on Gitea so once GitHub access is restored and repo-sync starts pushing, the file lands in the right place automatically.

Adding more cross-org defaults

GitHub also picks up <org>/.github/CONTRIBUTING.md, SECURITY.md, SUPPORT.md, issue / PR templates under .github/, and workflow templates under .github/workflow-templates/. Add as needed — keep them generic; per-repo overrides win.

Editing

PR against main; org-profile content is user-visible, so pair-review even trivial edits.