Repository navigation
docs(governance): maintainers, governance and support files - #155
Merged
Merged
Conversation
github-actions
Bot
added
dependencies
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the maintainer, governance and support files Guard Core TS was missing, and fixes the community files next to them that were stale or written for another language.
Added:
.github/ISSUE_TEMPLATE/bug.yml: issue form from the shared set, asking for this project's own runtime and versions.github/ISSUE_TEMPLATE/docs.yml: issue form from the shared set, asking for this project's own runtime and versions.github/ISSUE_TEMPLATE/feature.yml: issue form from the shared set, asking for this project's own runtime and versionsGOVERNANCE.md: how decisions are made, how a change lands (ruleset, admin merge for the approval count only), how releases workMAINTAINERS.md: who maintains the project and how to check that identity (GitHub profile, guard-core.com/company, the verified Guard-Core org domain, the registry metadata)SUPPORT.md: docs, questions, chat, issues and where security reports goChanged:
.github/ISSUE_TEMPLATE/config.yml: docs link to the docs site, plus Discord.SECURITY.md: there was no supported versions table (latest release v4.4.0). It now follows one policy across the organization: the current major gets bug and security fixes, the previous major security fixes only (4.x: bug and security fixes). The text is in first person, since one person maintains it.packages/core/package.json: author metadata nowRenzo Franceschini <rennf93@guard-core.com>, the same name and email as PyPI and Maven Central. The registry page shows it from the next release.packages/express/package.json: author metadata nowRenzo Franceschini <rennf93@guard-core.com>, the same name and email as PyPI and Maven Central. The registry page shows it from the next release.packages/fastify/package.json: author metadata nowRenzo Franceschini <rennf93@guard-core.com>, the same name and email as PyPI and Maven Central. The registry page shows it from the next release.packages/hono/package.json: author metadata nowRenzo Franceschini <rennf93@guard-core.com>, the same name and email as PyPI and Maven Central. The registry page shows it from the next release.packages/nestjs/package.json: author metadata nowRenzo Franceschini <rennf93@guard-core.com>, the same name and email as PyPI and Maven Central. The registry page shows it from the next release..github/ISSUE_TEMPLATE/bug_report.md: removed, replaced by the issue form of the same kind with the same fields..github/ISSUE_TEMPLATE/feature_request.md: removed, replaced by the issue form of the same kind with the same fields.Checked locally: every changed YAML, JSON and TOML file parses. No code changes.