Skip to content

Docs/community - #17

Merged
Jamkris merged 3 commits into
mainfrom
docs/community
Apr 10, 2026
Merged

Docs/community#17
Jamkris merged 3 commits into
mainfrom
docs/community

Conversation

@Jamkris

@Jamkris Jamkris commented Apr 10, 2026

Copy link
Copy Markdown
Owner

Summary by CodeRabbit

  • Documentation

    • Added a Code of Conduct defining expected community behavior and enforcement.
    • Added Contribution guidelines covering setup, development workflow, commit/PR standards, testing, i18n, and security reporting.
    • Added a Security policy describing reporting, response timelines, and secure handling of keys/config.
    • Added Korean-language contribution guidelines.
  • Chores

    • Improved release messaging with an extra informational command hint.

@coderabbitai

coderabbitai Bot commented Apr 10, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f3fdd292-f430-4935-99d0-e3d57a59b6c8

📥 Commits

Reviewing files that changed from the base of the PR and between 096b86a and a06822f.

📒 Files selected for processing (5)
  • CODE_OF_CONDUCT.md
  • CONTRIBUTING.md
  • SECURITY.md
  • docs/ko-KR/CONTRIBUTING.md
  • scripts/release.sh

Walkthrough

Added community and governance docs: Code of Conduct, CONTRIBUTING (EN + KO), SECURITY, plus a minor release script echo that outputs a one-line push + PR command for non-main branches.

Changes

Cohort / File(s) Summary
Community Guidelines
CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md
New docs: Contributor Covenant code of conduct; CONTRIBUTING covers setup, workflow, TypeScript/testing/i18n/conventional-commit rules and security/reporting; SECURITY defines supported versions, reporting process, SSH/git handling and secret-handling guidance.
Localized Documentation
docs/ko-KR/CONTRIBUTING.md
Korean translation of the CONTRIBUTING guide mirroring English requirements and development/testing/i18n/security rules.
Release Script
scripts/release.sh
Added a single echo line in the non-main branch section that prints a one-line git push origin $BRANCH && gh pr create ... command for creating the release PR.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

security

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Docs/community' is vague and doesn't clearly describe the specific changes being introduced. Use a more descriptive title that summarizes the main additions, such as 'Add Code of Conduct, Contributing, and Security documentation' or 'Add community guidelines and security policy'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/community

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 5

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CODE_OF_CONDUCT.md`:
- Line 58: Replace the template placeholder "{{ email }}" in CODE_OF_CONDUCT.md
with a real contact email address for reporting violations; locate the line
containing the text "reported by contacting the project team at {{ email }}.
All" and substitute "{{ email }}" with the project's designated contact (e.g.,
conduct@yourproject.org) so the document contains an actual, monitored address.

In `@docs/ko-KR/CONTRIBUTING.md`:
- Around line 83-86: Add a blank line before and after each fenced code block so
they render correctly; update the blocks containing the bash snippets (e.g., the
block with "git checkout -b feat/your-feature", the block with "npm run lint &&
npm run test:run", and the commit message example block referencing "[커밋 메시지
규칙]") to ensure there is an empty line immediately above the opening ``` and
immediately below the closing ```.
- Around line 51-62: Update the two fenced code blocks showing the project tree
and the commit message format to include a language identifier (e.g., use
```text) so syntax highlighting renders correctly; locate the fenced block
containing the project structure diagram (the ASCII tree under the heading
showing src/, tests/, scripts/, docs/) and the fenced block that shows the
commit message template/example (lines ~129-131) and change their opening fences
from ``` to ```text (or another appropriate language) to ensure proper
highlighting.

In `@scripts/release.sh`:
- Around line 91-92: The two echo helper lines containing "OneLine Commend)"
should be corrected to "OneLine Command)" and must not suggest pushing the
release tag from a feature branch; update the echoed examples that reference
BRANCH and VERSION so they only push the branch (git push origin $BRANCH) in the
pre-merge helper and move any git push origin v$VERSION (or instructions to
create a tag/release) to a post-merge or main-only helper—i.e., remove or
relocate "git push origin v$VERSION" from the one-line pre-merge echoes and
ensure the PR helper string with gh pr create only references the branch and
version bump text without pushing the tag.

In `@SECURITY.md`:
- Around line 46-48: The SECURITY.md claim about always creating a timestamped
backup is wrong because backups are only made when directories.length > 0 and
are created after modifications; fix add.ts and edit.ts to create the
timestamped backup unconditionally and before any modification functions are
called by moving or invoking the backup routine prior to calls to
removeIncludeIf() and generateProfileGitconfig(), and ensure the backup logic
does not depend on directories.length while preserving existing atomic writes
via writeGitconfigAtomic().
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 994e56b9-460a-4f6e-ad7e-7e3947c2c7d2

📥 Commits

Reviewing files that changed from the base of the PR and between 2ed4028 and 096b86a.

📒 Files selected for processing (5)
  • CODE_OF_CONDUCT.md
  • CONTRIBUTING.md
  • SECURITY.md
  • docs/ko-KR/CONTRIBUTING.md
  • scripts/release.sh

Comment thread CODE_OF_CONDUCT.md Outdated
Comment thread docs/ko-KR/CONTRIBUTING.md Outdated
Comment thread docs/ko-KR/CONTRIBUTING.md
Comment thread scripts/release.sh Outdated
Comment thread SECURITY.md
- Replace placeholder email with contact@jamkris.com in CODE_OF_CONDUCT
- Add language identifiers to fenced code blocks in CONTRIBUTING docs
- Fix typo "Commend" → "Command" and remove premature tag push in release script
- Correct backup description in SECURITY.md to match actual implementation
@Jamkris
Jamkris merged commit e235477 into main Apr 10, 2026
8 checks passed
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.

1 participant