Skip to content

Conversation

@sisyphus-dev-ai
Copy link
Collaborator

@sisyphus-dev-ai sisyphus-dev-ai commented Jan 6, 2026

Summary

This PR implements the requirements from #524:

  • Adds Language Policy section to CONTRIBUTING.md
  • Creates comprehensive GitHub issue templates with English requirement and doctor output mandate

Changes

CONTRIBUTING.md

  • Added "Language Policy" section after "Code of Conduct"
  • Explains English as the primary language for all communications
  • Provides supportive guidance for non-native speakers
  • Emphasizes global accessibility and consistency

GitHub Issue Templates

Created YAML-based issue forms with:

  1. config.yml: Template configuration with Discord and documentation links
  2. bug_report.yml:
    • Requires bunx oh-my-opencode doctor output (mandatory field)
    • Enforces English usage with helpful language policy notice
    • Collects comprehensive bug information
  3. feature_request.yml:
    • Optional doctor output field
    • Enforces English usage
    • Structured feature proposal form
  4. general.yml:
    • For questions and discussions
    • Optional doctor output
    • Enforces English usage

All templates include:

  • Language policy notice at the top
  • Prerequisites checklist
  • Clear field descriptions
  • Proper validation rules

Testing

  • ✅ All YAML files validated using js-yaml
  • ✅ Language policy section integrated naturally into CONTRIBUTING.md
  • ✅ Templates follow GitHub's issue form schema

Related Issues

Closes #524


Summary by cubic

Adds an English language policy and GitHub issue templates to standardize communication and improve triage. Addresses #524.

  • New Features

    • Added a Language Policy section to CONTRIBUTING.md with guidance for non‑native speakers.
    • Introduced GitHub issue forms: bug_report (requires bunx oh-my-opencode doctor), feature_request, and general; all include prerequisites and validation.
    • Added issue template config with Discord and documentation links.
  • Migration

    • Bug reports must include the doctor output.
    • All issues should be filed in English.

Written for commit d001d14. Summary will update on new commits.

- Add Language Policy section to CONTRIBUTING.md
  - Explain English as primary language
  - Provide guidance for non-native speakers
  - Emphasize accessibility and consistency

- Add GitHub issue templates (YAML forms)
  - Bug report template requiring 'bunx oh-my-opencode doctor' output
  - Feature request template
  - General question/discussion template
  - All templates enforce English usage with helpful guidance

Closes #524
required: true
- label: I am using the latest version of oh-my-opencode
required: true
- label: I have read the [documentation](https://github.com/code-yeongyu/oh-my-opencode#readme)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this part should be contributions md

@greptile-apps
Copy link

greptile-apps bot commented Jan 6, 2026

Greptile Summary

This PR implements an English language policy for the repository in response to issue #524, which was submitted in Korean. The changes add comprehensive GitHub issue templates that enforce English usage and require diagnostic output from bunx oh-my-opencode doctor for bug reports.

Major changes:

  • Added Language Policy section to CONTRIBUTING.md explaining the English requirement with supportive, inclusive language for non-native speakers
  • Created four YAML-based GitHub issue templates (bug_report.yml, feature_request.yml, general.yml, config.yml) that all include language policy notices at the top
  • Made bunx oh-my-opencode doctor output mandatory for bug reports (with examples), optional for feature requests and questions
  • All templates follow GitHub's issue form schema with proper validation, required fields, and clear descriptions
  • Disabled blank issues and added Discord/documentation links in config.yml

The implementation is thorough and well-structured, with consistent messaging across all templates. The language policy is presented in a welcoming, non-exclusionary manner that encourages contribution while maintaining consistency.

Confidence Score: 5/5

  • This PR is safe to merge with no issues found
  • All changes are documentation and configuration only with no code logic. The YAML templates follow GitHub's schema correctly, the language policy is well-written and inclusive, and the implementation directly addresses the requirements from issue 서브에이전트 미니맥스2.1 , glm-4.7 적용가능 문의드립니다. #524. No runtime impact or security concerns.
  • No files require special attention

Important Files Changed

Filename Overview
.github/ISSUE_TEMPLATE/bug_report.yml Comprehensive bug report template with mandatory bunx oh-my-opencode doctor output and English language policy notice
CONTRIBUTING.md Added comprehensive Language Policy section after Code of Conduct explaining English requirement with supportive guidance

Sequence Diagram

sequenceDiagram
    participant User
    participant GitHub
    participant IssueTemplate
    participant Contributor
    
    User->>GitHub: Navigate to create new issue
    GitHub->>IssueTemplate: Load issue template form
    IssueTemplate->>User: Display language policy notice
    IssueTemplate->>User: Show required/optional fields
    
    alt Bug Report
        User->>IssueTemplate: Select "Bug Report"
        IssueTemplate->>User: Require doctor output field
        User->>User: Run `bunx oh-my-opencode doctor`
        User->>IssueTemplate: Paste doctor output
        User->>IssueTemplate: Fill bug details in English
    else Feature Request
        User->>IssueTemplate: Select "Feature Request"
        IssueTemplate->>User: Optional doctor output field
        User->>IssueTemplate: Describe feature in English
    else Question/Discussion
        User->>IssueTemplate: Select "Question"
        IssueTemplate->>User: Optional doctor output field
        User->>IssueTemplate: Ask question in English
    end
    
    User->>GitHub: Submit issue
    GitHub->>GitHub: Validate required fields
    GitHub->>Contributor: Notify maintainers
    Contributor->>GitHub: Review issue with diagnostic info
    Contributor->>User: Respond to issue
Loading

@code-yeongyu
Copy link
Owner

@sisyphus-dev-ai hey just reflect my one comment

Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 5 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

@sisyphus-dev-ai sisyphus-dev-ai added the sisyphus: working Sisyphus is currently working on this label Jan 6, 2026
Remove duplicate Language Policy sections from issue templates and consolidate in CONTRIBUTING.md where it belongs
@sisyphus-dev-ai
Copy link
Collaborator Author

Comment reflected!

I've moved the Language Policy sections from all issue templates to where they belong.

Changes made:

  • Removed duplicate Language Policy markdown sections from:

The comprehensive Language Policy is now consolidated in (lines 29-51), which is the appropriate location for contribution guidelines.

Commit: a25afff

@sisyphus-dev-ai sisyphus-dev-ai removed the sisyphus: working Sisyphus is currently working on this label Jan 6, 2026
@code-yeongyu
Copy link
Owner

@sisyphus-dev-ai bro i said you to change readme part as contributions md

@sisyphus-dev-ai sisyphus-dev-ai added the sisyphus: working Sisyphus is currently working on this label Jan 6, 2026
- Add brief Language Policy notice at top of each issue template
- Reference CONTRIBUTING.md instead of duplicating full policy text
- Applies to bug_report.yml, feature_request.yml, and general.yml
@sisyphus-dev-ai
Copy link
Collaborator Author

Done!

I've updated all issue templates to reference CONTRIBUTING.md instead of duplicating the Language Policy text.

Changes made:

  • Added a brief Language Policy notice at the top of each issue template
  • Each notice links to the full Language Policy in CONTRIBUTING.md
  • Applied to: bug_report.yml, feature_request.yml, and general.yml

Example (from bug_report.yml):

- type: markdown
  attributes:
    value: |
      **Please write your issue in English.** See our [Language Policy](https://github.com/code-yeongyu/oh-my-opencode/blob/dev/CONTRIBUTING.md#language-policy) for details.

The Language Policy is now centralized in CONTRIBUTING.md and referenced (not duplicated) in the templates.

Commit: d001d14

@sisyphus-dev-ai sisyphus-dev-ai removed the sisyphus: working Sisyphus is currently working on this label Jan 6, 2026
@junhoyeo junhoyeo merged commit 5aa0ee1 into dev Jan 6, 2026
3 checks passed
@junhoyeo junhoyeo deleted the feat/language-policy-and-issue-templates branch January 6, 2026 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

서브에이전트 미니맥스2.1 , glm-4.7 적용가능 문의드립니다.

4 participants