chore: sync community files#78
Open
albert20260301 wants to merge 2 commits into
Open
Conversation
Contributor
Author
|
@francoischalifour could you review this? I picked you because recent CLI |
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.
What
Adds the four managed community files currently missing from the CLI repository: funding metadata, bug and feature issue forms, and the pull-request template.
Why
Keeps the CLI contribution surface consistent with the shared SDK templates. The existing
semantic-pull-request.ymlalready provides the required semantic-title guard with a pinned action and concurrency control, so this PR deliberately does not add a duplicate workflow.Validation
npx --yes prettier --check .github/FUNDING.yml .github/ISSUE_TEMPLATE/bug_report.yml .github/ISSUE_TEMPLATE/feature_request.yml .github/PULL_REQUEST_TEMPLATE.mdgit diff --checkNo runtime behavior, API surface, or release artifacts change.