docs: add community Code of Conduct with collaboration etiquette - #224
Open
soleil-colza wants to merge 5 commits into
Open
docs: add community Code of Conduct with collaboration etiquette#224soleil-colza wants to merge 5 commits into
soleil-colza wants to merge 5 commits into
Conversation
Adds CODE_OF_CONDUCT.md and CODE_OF_CONDUCT.ja.md at the repo root. The conduct baseline is adapted from Contributor Covenant 2.1 (with the required attribution); the collaboration etiquette section is Arkor-specific: issue claiming/assignment flow, no working on issues assigned to others, no duplicate PRs, and communication ground rules for interacting with maintainers and contributors. Links the new document from the Code of conduct sections of CONTRIBUTING.md and CONTRIBUTING.ja.md.
Code Review BotNo comment/code divergences or documentation drift detected. Reviewed 11 file(s); skipped 0. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📜 Recent review details⏰ Context from checks skipped due to timeout. (198)
🧰 Additional context used📓 Path-based instructions (4)**/{*.md,*.mdx,*.yaml,*.yml}📄 CodeRabbit inference engine (AGENTS.md)
Files:
**/*.{yaml,yml,md,json,html}📄 CodeRabbit inference engine (CONTRIBUTING.ja.md)
Files:
**/*📄 CodeRabbit inference engine (CONTRIBUTING.md)
Files:
CONTRIBUTING{,.ja}.md📄 CodeRabbit inference engine (AGENTS.md)
Files:
🧠 Learnings (3)📓 Common learnings📚 Learning: 2026-08-07T08:54:17.077ZApplied to files:
📚 Learning: 2026-08-07T08:54:24.838ZApplied to files:
🔇 Additional comments (4)
WalkthroughAdded English and Japanese Code of Conduct documents, updated contribution guidance and repository links, and included the documents in package publication and copying scripts. ChangesCommunity conduct documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: 🟡 Moderate · up to The new Code of Conduct directs reports to conduct@arkor.ai, but that address does not yet exist. Merge should wait until the alias is created or the documents name a working contact. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR Summary by QodoAdd bilingual Code of Conduct and link it from contributing docs
AI Description
Diagram
High-Level Assessment
Files changed (4)
|
Contributor
Greptile SummaryAdds bilingual Codes of Conduct and includes them with the contribution guides in both published packages.
Confidence Score: 5/5The PR appears safe to merge with no blocking failure remaining from the reviewed follow-up scope. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| CODE_OF_CONDUCT.md | Adds the English community conduct, collaboration, reporting, and enforcement policy. |
| CODE_OF_CONDUCT.ja.md | Adds the corresponding Japanese community policy. |
| packages/arkor/scripts/copy-root-files.mjs | Copies both contribution guides and Codes of Conduct into the package during supported builds. |
| packages/create-arkor/scripts/copy-root-files.mjs | Mirrors the package-document copy behavior for create-arkor. |
| packages/arkor/package.json | Adds the bilingual contribution and conduct documents to the published package allowlist. |
| packages/create-arkor/package.json | Adds the bilingual contribution and conduct documents to the published package allowlist. |
Reviews (4): Last reviewed commit: "docs: absolutize repo-only links in CONT..." | Re-trigger Greptile
Code Review by Qodo
1. No fallback CoC contact
|
![qodo-free-for-open-source-projects[bot]](https://avatars.githubusercontent.com/in/1068000?s=60&v=4){kind=small}
|
|
||
| Depending on severity and history, that action ranges from a private reminder of these rules, through removal of comments, unassignment of issues, or closing of PRs, up to temporary or permanent bans from project spaces. The maintainers' call is final. | ||
|
|
||
| To report a violation, email **conduct@arkor.ai**. For anything security-related, use security@arkor.ai instead (see [CONTRIBUTING.md](CONTRIBUTING.md)). All reports will be reviewed promptly and handled with as much confidentiality as the situation allows. Maintainers who do not enforce this Code of Conduct in good faith face the same consequences as anyone else. |
There was a problem hiding this comment.
1. No fallback coc contact 🐞 Bug ☼ Reliability
The new Code of Conduct files define **conduct@arkor.ai** as the sole non-security reporting channel, but do not document any fallback/private alternative if that mailbox is unavailable. This can leave contributors with no effective way to report Code of Conduct violations, blocking enforcement.
Agent Prompt
### Issue description
`CODE_OF_CONDUCT.md` / `CODE_OF_CONDUCT.ja.md` instruct reporters to email `conduct@arkor.ai`, but the repository does not document any fallback reporting route if that address is not reachable/monitored.
### Issue Context
Because this is community safety/reporting infrastructure, the repo should not publish a single-point-of-failure contact channel without either (a) ensuring it is definitely monitored, or (b) documenting a backup option.
### Fix Focus Areas
- CODE_OF_CONDUCT.md[60-66]
- CODE_OF_CONDUCT.ja.md[60-66]
### Expected change
- Either confirm `conduct@arkor.ai` is actively monitored and add a documented fallback (e.g., alternate email or another private reporting mechanism), **or** replace `conduct@arkor.ai` with an already-established monitored contact and keep the security-specific route as-is.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/arkorThe overall coverage in commit 81029c6 in the TypeScript / code-coverage/create-arkorThe overall coverage in commit 81029c6 in the TypeScript / code-coverage/cli-internalThe overall coverage in commit 81029c6 in the TypeScript / code-coverage/studio-appThe overall coverage in commit 81029c6 in the Updated |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 96b133c167
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| Depending on severity and history, that action ranges from a private reminder of these rules, through removal of comments, unassignment of issues, or closing of PRs, up to temporary or permanent bans from project spaces. The maintainers' call is final. | ||
|
|
||
| To report a violation, email **conduct@arkor.ai**. For anything security-related, use security@arkor.ai instead (see [CONTRIBUTING.md](CONTRIBUTING.md)). All reports will be reviewed promptly and handled with as much confidentiality as the situation allows. Maintainers who do not enforce this Code of Conduct in good faith face the same consequences as anyone else. |
There was a problem hiding this comment.
When someone follows this enforcement instruction to report harassment or another violation, the message will not reach the maintainers because the commit's own open question confirms that conduct@arkor.ai does not exist yet. Provision the alias or replace it with a monitored address before publishing this document; the same unavailable address also appears in the Japanese version.
Useful? React with 👍 / 👎.
| ## Code of conduct | ||
|
|
||
| Be kind, assume good faith, and keep technical disagreement technical. Anything else (harassment, personal attacks, exclusionary behavior) is grounds for being asked to leave. The maintainers' call is final. | ||
| All Arkor community spaces follow our [Code of Conduct](CODE_OF_CONDUCT.md). It also covers collaboration etiquette: how issues get claimed and assigned, how to avoid duplicate PRs, and how to communicate with maintainers. The short version: be kind, assume good faith, and keep technical disagreement technical. Anything else (harassment, personal attacks, exclusionary behavior) is grounds for being asked to leave. The maintainers' call is final. |
There was a problem hiding this comment.
During either published-package build, packages/*/scripts/copy-root-files.mjs copies this file into the package root, while both package manifests ship that copy without CODE_OF_CONDUCT.md. Consumers reading the packaged CONTRIBUTING.md therefore get a relative link whose target is absent; use a repository-absolute URL or include the target in both packages.
AGENTS.md reference: AGENTS.md:L118-L118
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CODE_OF_CONDUCT.ja.md`:
- Line 25: Update the Japanese harassment statement around 「望まれない性的な誘い」 to
explicitly cover both unwanted sexual advances and unwelcome sexual attention,
matching the broader scope of the English policy in CODE_OF_CONDUCT.md. Keep the
existing examples and surrounding wording unchanged.
- Line 66: Provide a working mailbox for Code of Conduct reports by creating
conduct@arkor.ai or selecting its replacement, then apply the finalized
reporting address consistently in both CODE_OF_CONDUCT documents and their
referenced contributing guidance.
In `@CODE_OF_CONDUCT.md`:
- Line 9: Split the pledge sentence in the Code of Conduct after “everyone,”
then begin the protected-characteristics list as a second sentence while
preserving the existing Contributor Covenant wording and content.
- Line 66: Provide a working Code of Conduct reporting mailbox by creating
conduct@arkor.ai or selecting its replacement, then apply the final reporting
address consistently in both Code of Conduct documents, including the
violation-reporting guidance.
🪄 Autofix
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 Plus
Run ID: dfc0c1ec-e048-4b5b-a86e-ae5a94d1f2f1
📒 Files selected for processing (4)
CODE_OF_CONDUCT.ja.mdCODE_OF_CONDUCT.mdCONTRIBUTING.ja.mdCONTRIBUTING.md
📜 Review details
⏰ Context from checks skipped due to timeout. (165)
- GitHub Check: cubic · AI code reviewer
- GitHub Check: install · pnpm-11 · macos-latest · node >=26.0.0 <27
- GitHub Check: install · pnpm-9 · macos-latest · node 26.0.0
- GitHub Check: install · npm · macos-latest · node >=24.12.0 <25
- GitHub Check: install · yarn · macos-latest · node >=26.0.0 <27
- GitHub Check: install · yarn-berry · macos-latest · node >=26.0.0 <27
- GitHub Check: install · bun · macos-latest · node >=26.0.0 <27
- GitHub Check: install · pnpm-11 · macos-latest · node 26.0.0
- GitHub Check: install · yarn · macos-latest · node 26.0.0
- GitHub Check: install · npm · macos-latest · node 24.12.0
- GitHub Check: install · bun · macos-latest · node 24.12.0
- GitHub Check: install · pnpm-11 · macos-latest · node 24.0.0
- GitHub Check: install · pnpm-11 · macos-latest · node 24.12.0
- GitHub Check: install · pnpm-9 · macos-latest · node >=24.12.0 <25
- GitHub Check: install · pnpm-10 · macos-latest · node >=24.12.0 <25
- GitHub Check: install · bun · macos-latest · node 24.0.0
- GitHub Check: install · pnpm-10 · macos-latest · node 24.12.0
- GitHub Check: install · pnpm-10 · macos-latest · node >=22.22.0 <23
- GitHub Check: install · yarn-berry · macos-latest · node 24.12.0
- GitHub Check: install · yarn · macos-latest · node >=22.22.0 <23
- GitHub Check: install · yarn · macos-latest · node 24.12.0
- GitHub Check: install · pnpm-11 · windows-latest · node 26.0.0
- GitHub Check: install · yarn-berry · macos-latest · node 22.22.0
- GitHub Check: install · pnpm-9 · macos-latest · node 24.12.0
- GitHub Check: install · pnpm-10 · macos-latest · node 24.0.0
- GitHub Check: install · yarn · macos-latest · node 22.22.0
- GitHub Check: install · bun · windows-latest · node 24.12.0
- GitHub Check: install · npm · macos-latest · node 24.0.0
- GitHub Check: install · yarn-berry · macos-latest · node >=22.22.0 <23
- GitHub Check: install · npm · macos-latest · node >=22.22.0 <23
- GitHub Check: install · pnpm-9 · macos-latest · node 24.0.0
- GitHub Check: install · pnpm-9 · windows-latest · node 24.12.0
- GitHub Check: install · bun · macos-latest · node 22.22.0
- GitHub Check: install · bun · macos-latest · node >=22.22.0 <23
- GitHub Check: install · npm · macos-latest · node 22.22.0
- GitHub Check: install · yarn · windows-latest · node 24.12.0
- GitHub Check: install · pnpm-11 · windows-latest · node 24.12.0
- GitHub Check: install · pnpm-11 · windows-latest · node >=26.0.0 <27
- GitHub Check: install · yarn-berry · windows-latest · node >=24.12.0 <25
- GitHub Check: install · yarn-berry · windows-latest · node >=26.0.0 <27
- GitHub Check: install · pnpm-10 · macos-latest · node 22.22.0
- GitHub Check: install · bun · windows-latest · node >=26.0.0 <27
- GitHub Check: install · yarn · macos-latest · node 24.0.0
- GitHub Check: install · yarn-berry · macos-latest · node 24.0.0
- GitHub Check: install · pnpm-11 · macos-latest · node >=22.22.0 <23
- GitHub Check: install · pnpm-9 · windows-latest · node >=26.0.0 <27
- GitHub Check: install · bun · windows-latest · node >=24.12.0 <25
- GitHub Check: install · pnpm-11 · windows-latest · node >=24.12.0 <25
- GitHub Check: install · npm · windows-latest · node >=26.0.0 <27
- GitHub Check: install · pnpm-11 · windows-latest · node 24.0.0
- GitHub Check: install · pnpm-9 · macos-latest · node >=22.22.0 <23
- GitHub Check: install · npm · windows-latest · node >=24.12.0 <25
- GitHub Check: install · pnpm-9 · windows-latest · node >=24.12.0 <25
- GitHub Check: install · pnpm-10 · windows-latest · node 24.12.0
- GitHub Check: install · pnpm-11 · macos-latest · node 22.22.0
- GitHub Check: install · yarn-berry · windows-latest · node 24.0.0
- GitHub Check: install · yarn · windows-latest · node >=26.0.0 <27
- GitHub Check: install · bun · windows-latest · node 26.0.0
- GitHub Check: install · pnpm-9 · macos-latest · node 22.22.0
- GitHub Check: install · pnpm-10 · windows-latest · node 24.0.0
- GitHub Check: install · pnpm-10 · windows-latest · node 26.0.0
- GitHub Check: install · npm · windows-latest · node 26.0.0
- GitHub Check: install · pnpm-9 · windows-latest · node 26.0.0
- GitHub Check: install · pnpm-10 · windows-latest · node >=26.0.0 <27
- GitHub Check: install · yarn · windows-latest · node 26.0.0
- GitHub Check: install · npm · windows-latest · node 24.12.0
- GitHub Check: install · yarn-berry · windows-latest · node 26.0.0
- GitHub Check: install · npm · windows-latest · node 24.0.0
- GitHub Check: install · yarn · windows-latest · node >=24.12.0 <25
- GitHub Check: install · pnpm-10 · windows-latest · node >=24.12.0 <25
- GitHub Check: install · yarn-berry · windows-latest · node 24.12.0
- GitHub Check: install · bun · windows-latest · node 24.0.0
- GitHub Check: install · yarn · windows-latest · node 24.0.0
- GitHub Check: install · bun · windows-latest · node >=22.22.0 <23
- GitHub Check: install · npm · windows-latest · node 22.22.0
- GitHub Check: install · bun · windows-latest · node 22.22.0
- GitHub Check: install · pnpm-9 · windows-latest · node >=22.22.0 <23
- GitHub Check: install · yarn · ubuntu-latest · node 26.0.0
- GitHub Check: install · yarn · ubuntu-latest · node 22.22.0
- GitHub Check: install · pnpm-11 · windows-latest · node >=22.22.0 <23
- GitHub Check: install · yarn · windows-latest · node 22.22.0
- GitHub Check: install · yarn · windows-latest · node >=22.22.0 <23
- GitHub Check: install · yarn-berry · windows-latest · node 22.22.0
- GitHub Check: install · yarn · ubuntu-latest · node >=26.0.0 <27
- GitHub Check: install · pnpm-11 · windows-latest · node 22.22.0
- GitHub Check: install · pnpm-10 · windows-latest · node 22.22.0
- GitHub Check: install · pnpm-10 · ubuntu-latest · node 24.12.0
- GitHub Check: install · npm · ubuntu-latest · node >=26.0.0 <27
- GitHub Check: install · pnpm-9 · windows-latest · node 22.22.0
- GitHub Check: install · yarn-berry · windows-latest · node >=22.22.0 <23
- GitHub Check: install · bun · ubuntu-latest · node >=26.0.0 <27
- GitHub Check: install · yarn-berry · ubuntu-latest · node 26.0.0
- GitHub Check: install · yarn-berry · ubuntu-latest · node >=26.0.0 <27
- GitHub Check: install · pnpm-9 · windows-latest · node 24.0.0
- GitHub Check: install · bun · ubuntu-latest · node 26.0.0
- GitHub Check: install · pnpm-10 · windows-latest · node >=22.22.0 <23
- GitHub Check: install · pnpm-9 · ubuntu-latest · node >=22.22.0 <23
- GitHub Check: install · npm · windows-latest · node >=22.22.0 <23
- GitHub Check: install · bun · ubuntu-latest · node >=24.12.0 <25
- GitHub Check: install · pnpm-9 · ubuntu-latest · node >=26.0.0 <27
- GitHub Check: install · pnpm-10 · ubuntu-latest · node >=26.0.0 <27
- GitHub Check: install · pnpm-11 · ubuntu-latest · node >=26.0.0 <27
- GitHub Check: install · yarn · ubuntu-latest · node >=24.12.0 <25
- GitHub Check: install · yarn · ubuntu-latest · node 24.0.0
- GitHub Check: install · npm · ubuntu-latest · node 26.0.0
- GitHub Check: install · yarn · ubuntu-latest · node 24.12.0
- GitHub Check: install · pnpm-9 · ubuntu-latest · node >=24.12.0 <25
- GitHub Check: install · yarn-berry · ubuntu-latest · node 24.12.0
- GitHub Check: install · npm · ubuntu-latest · node 24.0.0
- GitHub Check: install · pnpm-9 · ubuntu-latest · node 24.0.0
- GitHub Check: install · pnpm-9 · ubuntu-latest · node 24.12.0
- GitHub Check: install · pnpm-10 · ubuntu-latest · node 24.0.0
- GitHub Check: install · pnpm-11 · ubuntu-latest · node 24.0.0
- GitHub Check: install · pnpm-10 · ubuntu-latest · node 26.0.0
- GitHub Check: install · pnpm-9 · ubuntu-latest · node 26.0.0
- GitHub Check: install · bun · ubuntu-latest · node 22.22.0
- GitHub Check: install · npm · ubuntu-latest · node 22.22.0
- GitHub Check: install · yarn-berry · ubuntu-latest · node 24.0.0
- GitHub Check: install · npm · ubuntu-latest · node >=24.12.0 <25
- GitHub Check: install · pnpm-10 · ubuntu-latest · node 22.22.0
- GitHub Check: install · pnpm-9 · ubuntu-latest · node 22.22.0
- GitHub Check: install · yarn · ubuntu-latest · node >=22.22.0 <23
- GitHub Check: install · pnpm-11 · ubuntu-latest · node 22.22.0
- GitHub Check: install · pnpm-10 · ubuntu-latest · node >=22.22.0 <23
- GitHub Check: install · yarn-berry · ubuntu-latest · node 22.22.0
- GitHub Check: typecheck · lint · test · build · macos-latest · node >=24.12.0 <25
- GitHub Check: typecheck · lint · test · build · macos-latest · node 22.22.0
- GitHub Check: typecheck · lint · test · build · macos-latest · node >=24.8.0 <24.10.0
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=24.5.0 <24.8.0
- GitHub Check: typecheck · lint · test · build · macos-latest · node 26.0.0
- GitHub Check: coverage · upload to Codecov
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node >=24.12.0 <25
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node >=24.8.0 <24.10.0
- GitHub Check: typecheck · lint · test · build · macos-latest · node >=24.1.0 <24.3.0
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node >=24.10.0 <24.12.0
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node 26.0.0
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=24.10.0 <24.12.0
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=24.3.0 <24.5.0
- GitHub Check: typecheck · lint · test · build · macos-latest · node >=26.0.0 <27
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=24.1.0 <24.3.0
- GitHub Check: typecheck · lint · test · build · macos-latest · node >=24.10.0 <24.12.0
- GitHub Check: typecheck · lint · test · build · macos-latest · node >=24.0.0 <24.1.0
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=26.0.0 <27
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=24.0.0 <24.1.0
- GitHub Check: typecheck · lint · test · build · windows-latest · node 24.12.0
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=24.12.0 <25
- GitHub Check: typecheck · lint · test · build · macos-latest · node >=22.22.0 <23
- GitHub Check: typecheck · lint · test · build · macos-latest · node >=24.5.0 <24.8.0
- GitHub Check: typecheck · lint · test · build · windows-latest · node 26.0.0
- GitHub Check: typecheck · lint · test · build · macos-latest · node >=24.3.0 <24.5.0
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=24.8.0 <24.10.0
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node >=24.3.0 <24.5.0
- GitHub Check: typecheck · lint · test · build · macos-latest · node 24.12.0
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node 22.22.0
- GitHub Check: typecheck · lint · test · build · windows-latest · node 22.22.0
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node >=26.0.0 <27
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=22.22.0 <23
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node 24.12.0
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node >=24.1.0 <24.3.0
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node >=24.0.0 <24.1.0
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node >=24.5.0 <24.8.0
- GitHub Check: typecheck · lint · test · build · ubuntu-latest · node >=22.22.0 <23
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=22.22.0 <23
- GitHub Check: typecheck · lint · test · build · windows-latest · node >=24.1.0 <24.3.0
🧰 Additional context used
📓 Path-based instructions (4)
CONTRIBUTING{,.ja}.md
📄 CodeRabbit inference engine (AGENTS.md)
When editing
CONTRIBUTING.md, update the pairedCONTRIBUTING.ja.mdin the same change.
Files:
CONTRIBUTING.mdCONTRIBUTING.ja.md
**/{*.md,*.mdx,*.yaml,*.yml}
📄 CodeRabbit inference engine (AGENTS.md)
Do not format Markdown, MDX, YAML, or YML files with oxfmt; these are excluded because documentation anchors and deliberate YAML layout must remain hand-managed.
Files:
CONTRIBUTING.mdCONTRIBUTING.ja.mdCODE_OF_CONDUCT.mdCODE_OF_CONDUCT.ja.md
**/*
📄 CodeRabbit inference engine (CONTRIBUTING.ja.md)
**/*: コードのどこでもエムダッシュ (U+2014) は使いません。
Markdown (このファイルを含む) は ESLint ルールの対象外です。
Files:
CONTRIBUTING.mdCONTRIBUTING.ja.mdCODE_OF_CONDUCT.mdCODE_OF_CONDUCT.ja.md
**/*.{yaml,yml,md,json,html}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
To extend the same convention to yaml, md, json, html, and root-level config, the
scripts/check-no-em-dash.mtsrepo-wide guard scans every tracked file viagit grepand fails on the em-dash glyph or its HTML entity.
Files:
CONTRIBUTING.mdCONTRIBUTING.ja.mdCODE_OF_CONDUCT.mdCODE_OF_CONDUCT.ja.md
🧠 Learnings (5)
📓 Common learnings
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-07-24T09:55:04.181Z
Learning: Applies to CONTRIBUTING{,.ja}.md : When editing `CONTRIBUTING.md`, update the paired `CONTRIBUTING.ja.md` in the same change.
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-07-24T09:55:04.181Z
Learning: Applies to README{,.ja}.md : When editing `README.md`, update the paired `README.ja.md` in the same change.
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-07-24T09:55:04.181Z
Learning: Applies to docs/**/*.mdx : Keep English and Japanese documentation paired: changes under `docs/` must also update the corresponding files under `docs/ja/`. Verify Mintlify-generated anchors before adding cross-page links; preserve `/`, `=`, and full-width parentheses while accounting for stripped ASCII punctuation and backticks.
Learnt from: CR
Repo: arkorlab/arkor
Timestamp: 2026-08-12T03:43:42.646Z
Learning: If you have an idea for a non-trivial change (new SDK factory, CLI command, Studio view), please open an issue first so we can align on the API shape before you write code.
📚 Learning: 2026-07-24T09:55:04.181Z
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-07-24T09:55:04.181Z
Learning: Applies to CONTRIBUTING{,.ja}.md : When editing `CONTRIBUTING.md`, update the paired `CONTRIBUTING.ja.md` in the same change.
Applied to files:
CONTRIBUTING.ja.mdCODE_OF_CONDUCT.ja.md
📚 Learning: 2026-07-24T09:55:04.181Z
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-07-24T09:55:04.181Z
Learning: Applies to README{,.ja}.md : When editing `README.md`, update the paired `README.ja.md` in the same change.
Applied to files:
CONTRIBUTING.ja.mdCODE_OF_CONDUCT.ja.md
📚 Learning: 2026-08-07T08:54:24.838Z
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: CONTRIBUTING.ja.md:0-0
Timestamp: 2026-08-07T08:54:24.838Z
Learning: 新しい SDK ファクトリ、CLI コマンド、Studio ビューなどの非自明な変更は、実装前に Issue で API の形について合意を得る。
Applied to files:
CONTRIBUTING.ja.md
📚 Learning: 2026-08-07T08:54:24.838Z
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: CONTRIBUTING.ja.md:0-0
Timestamp: 2026-08-07T08:54:24.838Z
Learning: 貢献物はリポジトリの LICENSE.md に定めるライセンスの下で公開されることに同意する。
Applied to files:
CONTRIBUTING.ja.md
🪛 LanguageTool
CODE_OF_CONDUCT.md
[style] ~8-~8: This sentence is over 40 words long. Consider splitting it up, as shorter sentences make the text easier to read.
Context: ...ers). Both are binding. ## Our pledge We as members, contributors, and maintainers pledge to make participation in the Arkor community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. We pledge to act and interact in ways ...
(TOO_LONG_SENTENCE)
[style] ~26-~26: Try using a synonym here to strengthen your wording.
Context: ...on. - Trolling, insulting or derogatory comments, and personal or political attacks. - P...
(COMMENT_REMARK)
[style] ~45-~45: Since ownership is already implied, this phrasing may be redundant.
Context: ... weigh in. Do not silently race it with your own PR. - Link the issue. Reference the...
(PRP_OWN)
🔇 Additional comments (5)
CODE_OF_CONDUCT.md (2)
1-8: LGTM!Also applies to: 10-65, 68-70
66-66: 🔒 Security & Privacy | 🟠 Major | ⚡ Quick winUse one confirmed reporting channel in both conduct policies.
The same unavailable
conduct@arkor.aiaddress appears in both documents. Contributors cannot report violations until the mailbox exists or the address is replaced.
CODE_OF_CONDUCT.md#L66-L66: createconduct@arkor.aior replace it with a working address.CODE_OF_CONDUCT.ja.md#L66-L66: apply the same contact change in the Japanese policy.The PR objective states that
conduct@arkor.aimust be created or replaced before merge.⛔ Skipped due to learnings
Learnt from: CR Repo: arkorlab/arkor PR: 0 File: AGENTS.md:0-0 Timestamp: 2026-07-24T09:55:04.181Z Learning: Applies to CONTRIBUTING{,.ja}.md : When editing `CONTRIBUTING.md`, update the paired `CONTRIBUTING.ja.md` in the same change.Learnt from: CR Repo: arkorlab/arkor PR: 0 File: CONTRIBUTING.md:0-0 Timestamp: 2026-08-07T08:54:17.077Z Learning: Report security issues privately by emailing securityarkor.ai instead of filing a public issue.Learnt from: CR Repo: arkorlab/arkor PR: 0 File: CONTRIBUTING.ja.md:0-0 Timestamp: 2026-08-07T08:54:24.838Z Learning: セキュリティ問題は公開 GitHub Issue ではなく securityarkor.ai に報告する。CODE_OF_CONDUCT.ja.md (1)
1-24: LGTM!Also applies to: 26-65, 68-70
CONTRIBUTING.md (1)
131-131: LGTM!CONTRIBUTING.ja.md (1)
130-130: LGTM!
|
|
||
| 深刻度と経緯に応じて、その措置は、このルールの非公開でのリマインドから、コメントの削除、Issue のアサイン解除、PR のクローズ、そしてプロジェクトスペースからの一時的または恒久的な追放までの範囲に及びます。メンテナーの判断が最終です。 | ||
|
|
||
| 違反を報告するには、**conduct@arkor.ai** へメールしてください。セキュリティに関わる内容は代わりに security@arkor.ai を使ってください ([CONTRIBUTING.ja.md](CONTRIBUTING.ja.md) を参照)。すべての報告は速やかに確認され、状況が許す限りの機密性をもって扱われます。この行動規範を誠実に執行しないメンテナーも、他の全員と同じ措置の対象になります。 |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Provide a working conduct-reporting address before merge.
conduct@arkor.ai is the only reporting channel for Code of Conduct violations, but the PR objective states that this address does not yet exist. Create the mailbox or replace the address, then apply the final value in both conduct documents.
The PR objective states that conduct@arkor.ai must be created or replaced before merge.
[skip_comment]
⛔ Skipped due to learnings
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: CONTRIBUTING.md:0-0
Timestamp: 2026-08-07T08:54:17.077Z
Learning: Report security issues privately by emailing securityarkor.ai instead of filing a public issue.
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: CONTRIBUTING.ja.md:0-0
Timestamp: 2026-08-07T08:54:24.838Z
Learning: セキュリティ問題は公開 GitHub Issue ではなく securityarkor.ai に報告する。
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CODE_OF_CONDUCT.ja.md` at line 66, Provide a working mailbox for Code of
Conduct reports by creating conduct@arkor.ai or selecting its replacement, then
apply the finalized reporting address consistently in both CODE_OF_CONDUCT
documents and their referenced contributing guidance.
|
|
||
| ## Our pledge | ||
|
|
||
| We as members, contributors, and maintainers pledge to make participation in the Arkor community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win
Split the pledge sentence for readability.
Line 9 contains a long list of protected characteristics in one sentence. Split the sentence after everyone and place the list in a second sentence. Preserve the Contributor Covenant wording.
LanguageTool flagged this sentence as longer than 40 words.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CODE_OF_CONDUCT.md` at line 9, Split the pledge sentence in the Code of
Conduct after “everyone,” then begin the protected-characteristics list as a
second sentence while preserving the existing Contributor Covenant wording and
content.
Source: Linters/SAST tools
|
|
||
| Depending on severity and history, that action ranges from a private reminder of these rules, through removal of comments, unassignment of issues, or closing of PRs, up to temporary or permanent bans from project spaces. The maintainers' call is final. | ||
|
|
||
| To report a violation, email **conduct@arkor.ai**. For anything security-related, use security@arkor.ai instead (see [CONTRIBUTING.md](CONTRIBUTING.md)). All reports will be reviewed promptly and handled with as much confidentiality as the situation allows. Maintainers who do not enforce this Code of Conduct in good faith face the same consequences as anyone else. |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Provide a working conduct-reporting address before merge.
conduct@arkor.ai is the only reporting channel for Code of Conduct violations, but the PR objective states that this address does not yet exist. Create the mailbox or replace the address, then apply the final value in both conduct documents.
The PR objective states that conduct@arkor.ai must be created or replaced before merge.
[skip_comment]
⛔ Skipped due to learnings
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: CONTRIBUTING.md:0-0
Timestamp: 2026-08-07T08:54:17.077Z
Learning: Report security issues privately by emailing securityarkor.ai instead of filing a public issue.
Learnt from: CR
Repo: arkorlab/arkor PR: 0
File: CONTRIBUTING.ja.md:0-0
Timestamp: 2026-08-07T08:54:24.838Z
Learning: セキュリティ問題は公開 GitHub Issue ではなく securityarkor.ai に報告する。
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CODE_OF_CONDUCT.md` at line 66, Provide a working Code of Conduct reporting
mailbox by creating conduct@arkor.ai or selecting its replacement, then apply
the final reporting address consistently in both Code of Conduct documents,
including the violation-reporting guidance.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
2 issues found across 4 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="CODE_OF_CONDUCT.md">
<violation number="1" location="CODE_OF_CONDUCT.md:66">
P1: The enforcement section instructs users to report violations to conduct@arkor.ai, which does not exist yet (acknowledged in the PR description). Reports to a bouncing address are silently lost, defeating the Code of Conduct's reporting mechanism; create the alias or point to an existing contact before merging.</violation>
</file>
<file name="CODE_OF_CONDUCT.ja.md">
<violation number="1" location="CODE_OF_CONDUCT.ja.md:66">
P2: The report address conduct@arkor.ai does not exist — violations reported there would go nowhere, breaking the CoC's only enforcement channel. Create the alias or point to a working contact before merging.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
|
|
||
| Depending on severity and history, that action ranges from a private reminder of these rules, through removal of comments, unassignment of issues, or closing of PRs, up to temporary or permanent bans from project spaces. The maintainers' call is final. | ||
|
|
||
| To report a violation, email **conduct@arkor.ai**. For anything security-related, use security@arkor.ai instead (see [CONTRIBUTING.md](CONTRIBUTING.md)). All reports will be reviewed promptly and handled with as much confidentiality as the situation allows. Maintainers who do not enforce this Code of Conduct in good faith face the same consequences as anyone else. |
There was a problem hiding this comment.
P1: The enforcement section instructs users to report violations to conduct@arkor.ai, which does not exist yet (acknowledged in the PR description). Reports to a bouncing address are silently lost, defeating the Code of Conduct's reporting mechanism; create the alias or point to an existing contact before merging.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At CODE_OF_CONDUCT.md, line 66:
<comment>The enforcement section instructs users to report violations to conduct@arkor.ai, which does not exist yet (acknowledged in the PR description). Reports to a bouncing address are silently lost, defeating the Code of Conduct's reporting mechanism; create the alias or point to an existing contact before merging.</comment>
<file context>
@@ -0,0 +1,70 @@
+
+Depending on severity and history, that action ranges from a private reminder of these rules, through removal of comments, unassignment of issues, or closing of PRs, up to temporary or permanent bans from project spaces. The maintainers' call is final.
+
+To report a violation, email **conduct@arkor.ai**. For anything security-related, use security@arkor.ai instead (see [CONTRIBUTING.md](CONTRIBUTING.md)). All reports will be reviewed promptly and handled with as much confidentiality as the situation allows. Maintainers who do not enforce this Code of Conduct in good faith face the same consequences as anyone else.
+
+## Attribution
</file context>
|
|
||
| 深刻度と経緯に応じて、その措置は、このルールの非公開でのリマインドから、コメントの削除、Issue のアサイン解除、PR のクローズ、そしてプロジェクトスペースからの一時的または恒久的な追放までの範囲に及びます。メンテナーの判断が最終です。 | ||
|
|
||
| 違反を報告するには、**conduct@arkor.ai** へメールしてください。セキュリティに関わる内容は代わりに security@arkor.ai を使ってください ([CONTRIBUTING.ja.md](CONTRIBUTING.ja.md) を参照)。すべての報告は速やかに確認され、状況が許す限りの機密性をもって扱われます。この行動規範を誠実に執行しないメンテナーも、他の全員と同じ措置の対象になります。 |
There was a problem hiding this comment.
P2: The report address conduct@arkor.ai does not exist — violations reported there would go nowhere, breaking the CoC's only enforcement channel. Create the alias or point to a working contact before merging.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At CODE_OF_CONDUCT.ja.md, line 66:
<comment>The report address conduct@arkor.ai does not exist — violations reported there would go nowhere, breaking the CoC's only enforcement channel. Create the alias or point to a working contact before merging.</comment>
<file context>
@@ -0,0 +1,70 @@
+
+深刻度と経緯に応じて、その措置は、このルールの非公開でのリマインドから、コメントの削除、Issue のアサイン解除、PR のクローズ、そしてプロジェクトスペースからの一時的または恒久的な追放までの範囲に及びます。メンテナーの判断が最終です。
+
+違反を報告するには、**conduct@arkor.ai** へメールしてください。セキュリティに関わる内容は代わりに security@arkor.ai を使ってください ([CONTRIBUTING.ja.md](CONTRIBUTING.ja.md) を参照)。すべての報告は速やかに確認され、状況が許す限りの機密性をもって扱われます。この行動規範を誠実に執行しないメンテナーも、他の全員と同じ措置の対象になります。
+
+## 帰属 (Attribution)
</file context>
k-taro56
reviewed
Aug 12, 2026
k-taro56
left a comment
k-taro56
left a comment
Contributor
There was a problem hiding this comment.
I think it would be good to clarify that an issue isn’t necessarily required before creating a PR
| @@ -0,0 +1,70 @@ | |||
| # 行動規範 (Code of Conduct) | |||
|
|
|||
| Arkor はオープンに開発されています。TypeScript ネイティブなファインチューニングを実現したい人たちと一緒に、その人たちのために作られています。このドキュメントは、Arkor のすべてのコミュニティスペースでお互いにどう接するかを定めたものです: この GitHub リポジトリ (Issue、プルリクエスト、Discussions)、[Discord サーバー](https://discord.gg/YujCZYGrEZ)、そしてプロジェクトを代表して発信・参加するすべての公式アカウントやイベントが対象です。 | |||
Contributor
There was a problem hiding this comment.
Suggested change
| Arkor はオープンに開発されています。TypeScript ネイティブなファインチューニングを実現したい人たちと一緒に、その人たちのために作られています。このドキュメントは、Arkor のすべてのコミュニティスペースでお互いにどう接するかを定めたものです: この GitHub リポジトリ (Issue、プルリクエスト、Discussions)、[Discord サーバー](https://discord.gg/YujCZYGrEZ)、そしてプロジェクトを代表して発信・参加するすべての公式アカウントやイベントが対象です。 | |
| Arkor はオープンに開発されています。TypeScript ネイティブなファインチューニングを実現したい人たちと一緒に、その人たちのために作られています。このドキュメントは、Arkor のすべてのコミュニティースペースでお互いにどう接するかを定めたものです。この GitHub リポジトリー（Issue、プルリクエスト、Discussions）、[Discord サーバー](https://discord.arkor.ai)、そしてプロジェクトを代表して発信・参加するすべての公式アカウントやイベントが対象です。 |
|
|
||
| ## 私たちの誓い | ||
|
|
||
| メンバー、コントリビューター、メンテナーである私たちは、年齢、体格、目に見える・見えない障害、民族、性的特徴、性自認と性表現、経験の程度、学歴、社会経済的地位、国籍、外見、人種、宗教、性的アイデンティティと性的指向にかかわらず、すべての人にとってハラスメントのない参加体験を Arkor コミュニティで実現することを誓います。 |
Contributor
There was a problem hiding this comment.
Suggested change
| メンバー、コントリビューター、メンテナーである私たちは、年齢、体格、目に見える・見えない障害、民族、性的特徴、性自認と性表現、経験の程度、学歴、社会経済的地位、国籍、外見、人種、宗教、性的アイデンティティと性的指向にかかわらず、すべての人にとってハラスメントのない参加体験を Arkor コミュニティで実現することを誓います。 | |
| メンバー、コントリビューター、メンテナーである私たちは、年齢、体格、目に見える・見えない障害、民族、性的特徴、性自認と性表現、経験の程度、学歴、社会経済的地位、国籍、外見、人種、宗教、性的アイデンティティーと性的指向にかかわらず、すべての人にとってハラスメントのない参加体験を Arkor コミュニティーで実現することを誓います。 |
|
|
||
| メンバー、コントリビューター、メンテナーである私たちは、年齢、体格、目に見える・見えない障害、民族、性的特徴、性自認と性表現、経験の程度、学歴、社会経済的地位、国籍、外見、人種、宗教、性的アイデンティティと性的指向にかかわらず、すべての人にとってハラスメントのない参加体験を Arkor コミュニティで実現することを誓います。 | ||
|
|
||
| 私たちは、オープンで、歓迎的で、多様で、インクルーシブで、健全なコミュニティに貢献するように行動し、交流することを誓います。 |
Contributor
There was a problem hiding this comment.
Suggested change
| 私たちは、オープンで、歓迎的で、多様で、インクルーシブで、健全なコミュニティに貢献するように行動し、交流することを誓います。 | |
| 私たちは、オープンで、歓迎的で、多様で、インクルーシブで、健全なコミュニティーに貢献するように行動し、交流することを誓います。 |
| - 誠実さを仮定し、技術的な意見の相違を技術的なまま保つこと。 | ||
| - 建設的なフィードバックを与え、また素直に受け入れること。 | ||
| - 責任を受け入れ、自分の間違いによって影響を受けた人に謝罪し、その経験から学ぶこと。 | ||
| - 自分だけでなく、コミュニティとプロジェクトにとって何が最善かに目を向けること。 |
Contributor
There was a problem hiding this comment.
Suggested change
| - 自分だけでなく、コミュニティとプロジェクトにとって何が最善かに目を向けること。 | |
| - 自分だけでなく、コミュニティーとプロジェクトにとって何が最善かに目を向けること。 |
| メンテナーとコントリビューターは、自分の時間を提供している人たちです。協働する仲間であって、あなた専属のサポート窓口ではなく、友達になる義務もありません。 | ||
|
|
||
| - **公開の場で、本題に沿って。** 質問は Issue、Discussions、または Discord の公開チャンネルでしてください。招待されていない限り、コードレビュー、マージの依頼、アサインの依頼、一般的なサポートを目的としてメンテナーやコントリビューターに DM を送らないでください。 | ||
| - **スパムと催促の連投はしない。** 同じ人への繰り返しのメンション、毎日の「進捗どうですか?」、プロジェクトの場と無関係な雑談・自己宣伝・仕事の勧誘はやめてください。1 週間ほど動きがなければ、該当スレッドで丁寧に一度だけリマインドするのは問題ありません。 |
Contributor
There was a problem hiding this comment.
Suggested change
| - **スパムと催促の連投はしない。** 同じ人への繰り返しのメンション、毎日の「進捗どうですか?」、プロジェクトの場と無関係な雑談・自己宣伝・仕事の勧誘はやめてください。1 週間ほど動きがなければ、該当スレッドで丁寧に一度だけリマインドするのは問題ありません。 | |
| - **スパムと催促の連投はしない。** 同じ人への繰り返しのメンション、毎日の「進捗どうですか？」、プロジェクトの場と無関係な雑談・自己宣伝・仕事の勧誘はやめてください。1 週間ほど動きがなければ、該当スレッドで丁寧に一度だけリマインドするのは問題ありません。 |
|
|
||
| - **1 Issue に 1 PR、重複は作らない。** PR を開く前に、同じ Issue や同じ変更に対するオープンな PR がないか検索してください。既に存在する場合は、競合する PR を新しく開くのではなく、そちらに協力してください (レビューする、コメントする、動作確認する)。重複した PR は、最も早くからアクティブなものを優先してクローズします。 | ||
| - **別のアプローチがあるなら、まず議論。** 既存の PR の方向性が間違っていると思う場合は、その Issue または PR 上で代替案を説明し、メンテナーの判断を仰いでください。黙って自分の PR で追い抜こうとしないでください。 | ||
| - **Issue をリンクする。** PR が対応する Issue を参照してください (`Closes #123`)。アサインと重複のチェックが容易になります。 |
Contributor
There was a problem hiding this comment.
Suggested change
| - **Issue をリンクする。** PR が対応する Issue を参照してください (`Closes #123`)。アサインと重複のチェックが容易になります。 | |
| - **Issue をリンクする。** PR が対応する Issue を参照してください（`Closes #123`）。アサインと重複のチェックが容易になります。 |
|
|
||
| ### プルリクエスト | ||
|
|
||
| - **1 Issue に 1 PR、重複は作らない。** PR を開く前に、同じ Issue や同じ変更に対するオープンな PR がないか検索してください。既に存在する場合は、競合する PR を新しく開くのではなく、そちらに協力してください (レビューする、コメントする、動作確認する)。重複した PR は、最も早くからアクティブなものを優先してクローズします。 |
Contributor
There was a problem hiding this comment.
Suggested change
| - **1 Issue に 1 PR、重複は作らない。** PR を開く前に、同じ Issue や同じ変更に対するオープンな PR がないか検索してください。既に存在する場合は、競合する PR を新しく開くのではなく、そちらに協力してください (レビューする、コメントする、動作確認する)。重複した PR は、最も早くからアクティブなものを優先してクローズします。 | |
| - **1 Issue に 1 PR、重複は作らない。** PR を開く前に、同じ Issue や同じ変更に対するオープンな PR がないか検索してください。既に存在する場合は、競合する PR を新しく開くのではなく、そちらに協力してください（レビューする、コメントする、動作確認する）。重複した PR は、最も早くからアクティブなものを優先してクローズします。 |
|
|
||
| - 公開・非公開を問わず、あらゆる形のハラスメント。性的な言葉や画像の使用、望まれない性的な誘いを含みます。 | ||
| - トローリング、侮辱的・軽蔑的なコメント、個人攻撃や政治的な攻撃。 | ||
| - 明示的な許可のない、他者の個人情報 (住所やメールアドレスなど) の公開。 |
Contributor
There was a problem hiding this comment.
Suggested change
| - 明示的な許可のない、他者の個人情報 (住所やメールアドレスなど) の公開。 | |
| - 明示的な許可のない、他者の個人情報（住所やメールアドレスなど）の公開。 |
|
|
||
| Arkor はオープンに開発されています。TypeScript ネイティブなファインチューニングを実現したい人たちと一緒に、その人たちのために作られています。このドキュメントは、Arkor のすべてのコミュニティスペースでお互いにどう接するかを定めたものです: この GitHub リポジトリ (Issue、プルリクエスト、Discussions)、[Discord サーバー](https://discord.gg/YujCZYGrEZ)、そしてプロジェクトを代表して発信・参加するすべての公式アカウントやイベントが対象です。 | ||
|
|
||
| この文書は 2 つの部分からなります: **どう振る舞うか** (行動の基準) と、**どう協働するか** (Issue・プルリクエスト・メンテナーとのやりとりのエチケット) です。どちらも守るべきルールです。 |
Contributor
There was a problem hiding this comment.
Suggested change
| この文書は 2 つの部分からなります: **どう振る舞うか** (行動の基準) と、**どう協働するか** (Issue・プルリクエスト・メンテナーとのやりとりのエチケット) です。どちらも守るべきルールです。 | |
| この文書は 2 つの部分からなります: **どう振る舞うか**（行動の基準）と、**どう協働するか**（Issue・プルリクエスト・メンテナーとのやりとりのエチケット）です。どちらも守るべきルールです。 |
| @@ -0,0 +1,70 @@ | |||
| # 行動規範 (Code of Conduct) | |||
Contributor
There was a problem hiding this comment.
Suggested change
| # 行動規範 (Code of Conduct) | |
| # 行動規範（Code of Conduct） |
- Apply reviewer suggestions on the Japanese documents: long-vowel katakana forms, full-width parentheses and question mark, sentence punctuation, and the discord.arkor.ai vanity URL (mirrored in the English document so the pair stays in sync). - Broaden the Japanese harassment wording to cover unwelcome sexual attention as well as advances, matching the English policy. - Ship CODE_OF_CONDUCT.md and CODE_OF_CONDUCT.ja.md in both published tarballs via copy-root-files.mjs, package.json files, and .gitignore, so the packaged CONTRIBUTING.md link resolves.
![drift-check[bot]](https://avatars.githubusercontent.com/in/4198242?s=60&v=4){kind=small}
There was a problem hiding this comment.
Documentation drift
Code Review Bot flagged 1 possible documentation drift(s). These are advisory.
AGENTS.md(info):The 'Generated files' bullet in the 'Non-obvious gotchas' section lists 'packages/*/CONTRIBUTING.md' and 'packages/arkor/docs/', but it omits 'packages/*/CODE_OF_CONDUCT.md' and 'packages/*/CODE_OF_CONDUCT.ja.md' which are now copied to package directories as seen in 'packages/arkor/scripts/copy-root-files.mjs'.— suggested:Update the 'Generated files' bullet in the 'Non-obvious gotchas' section to: "- **Generated files** copied into package dirs are gitignored: 'packages/*/CONTRIBUTING.md' (from root), 'packages/*/README.ja.md' (from root), 'packages/*/CODE_OF_CONDUCT.md' (from root), and 'packages/*/CODE_OF_CONDUCT.ja.md' (from root). Edit the source under repo root, not the copies."
Results are for commit 968e285. On newer commits, the bot's summary comment reflects the latest run.
|
Code review by qodo was updated up to the latest commit 968e285 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 968e2851ec
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "README.ja.md" | ||
| "README.ja.md", | ||
| "CODE_OF_CONDUCT.md", | ||
| "CODE_OF_CONDUCT.ja.md" |
There was a problem hiding this comment.
When either package is published, CODE_OF_CONDUCT.ja.md is included but its three relative links to CONTRIBUTING.ja.md are broken because neither copy-root-files.mjs nor either package's files list includes that target. Add CONTRIBUTING.ja.md to both copy/package lists, or make those links repository-absolute.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
2 issues found across 8 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="CODE_OF_CONDUCT.md">
<violation number="1" location="CODE_OF_CONDUCT.md:3">
P3: This change points the Code of Conduct's Discord link to https://discord.arkor.ai (which resolves to invite code WjpUu5QsGZ), while every other Discord reference in the repo — README.md, README.ja.md, CONTRIBUTING.md, and CONTRIBUTING.ja.md — still uses https://discord.gg/YujCZYGrEZ. The community now sees two different invite links depending on which doc they read. Align them: either keep the existing discord.gg/YujCZYGrEZ here or, if discord.arkor.ai is the intended branded link, update the other four files in this same PR.</violation>
</file>
<file name="packages/arkor/package.json">
<violation number="1" location="packages/arkor/package.json:41">
P3: THE Japanese Code of Conduct is now shipped in the published tarball, but it contains three relative links to `CONTRIBUTING.ja.md` (lines 49, 58, 66), which is not included in either copy-root-files.mjs FILES list or the package `files` array. In the npm tarball those links resolve to a file that does not exist. Add `CONTRIBUTING.ja.md` to the copy script and both packages' `files` arrays (and .gitignore) so the shipped Japanese CoC links stay valid, or the links will be broken in node_modules.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| @@ -0,0 +1,70 @@ | |||
| # Code of Conduct | |||
|
|
|||
| Arkor is built in the open, with and for people who want TypeScript-native fine-tuning to exist. This document describes how we treat each other in every Arkor community space: this GitHub repository (issues, pull requests, discussions), the [Discord server](https://discord.arkor.ai), and any official account or event where someone represents the project. | |||
There was a problem hiding this comment.
P3: This change points the Code of Conduct's Discord link to https://discord.arkor.ai (which resolves to invite code WjpUu5QsGZ), while every other Discord reference in the repo — README.md, README.ja.md, CONTRIBUTING.md, and CONTRIBUTING.ja.md — still uses https://discord.gg/YujCZYGrEZ. The community now sees two different invite links depending on which doc they read. Align them: either keep the existing discord.gg/YujCZYGrEZ here or, if discord.arkor.ai is the intended branded link, update the other four files in this same PR.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At CODE_OF_CONDUCT.md, line 3:
<comment>This change points the Code of Conduct's Discord link to https://discord.arkor.ai (which resolves to invite code WjpUu5QsGZ), while every other Discord reference in the repo — README.md, README.ja.md, CONTRIBUTING.md, and CONTRIBUTING.ja.md — still uses https://discord.gg/YujCZYGrEZ. The community now sees two different invite links depending on which doc they read. Align them: either keep the existing discord.gg/YujCZYGrEZ here or, if discord.arkor.ai is the intended branded link, update the other four files in this same PR.</comment>
<file context>
@@ -1,6 +1,6 @@
# Code of Conduct
-Arkor is built in the open, with and for people who want TypeScript-native fine-tuning to exist. This document describes how we treat each other in every Arkor community space: this GitHub repository (issues, pull requests, discussions), the [Discord server](https://discord.gg/YujCZYGrEZ), and any official account or event where someone represents the project.
+Arkor is built in the open, with and for people who want TypeScript-native fine-tuning to exist. This document describes how we treat each other in every Arkor community space: this GitHub repository (issues, pull requests, discussions), the [Discord server](https://discord.arkor.ai), and any official account or event where someone represents the project.
It has two parts: **how we behave** (the conduct baseline) and **how we collaborate** (etiquette for issues, pull requests, and talking to maintainers). Both are binding.
</file context>
| "README.ja.md" | ||
| "README.ja.md", | ||
| "CODE_OF_CONDUCT.md", | ||
| "CODE_OF_CONDUCT.ja.md" |
There was a problem hiding this comment.
P3: THE Japanese Code of Conduct is now shipped in the published tarball, but it contains three relative links to CONTRIBUTING.ja.md (lines 49, 58, 66), which is not included in either copy-root-files.mjs FILES list or the package files array. In the npm tarball those links resolve to a file that does not exist. Add CONTRIBUTING.ja.md to the copy script and both packages' files arrays (and .gitignore) so the shipped Japanese CoC links stay valid, or the links will be broken in node_modules.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/arkor/package.json, line 41:
<comment>THE Japanese Code of Conduct is now shipped in the published tarball, but it contains three relative links to `CONTRIBUTING.ja.md` (lines 49, 58, 66), which is not included in either copy-root-files.mjs FILES list or the package `files` array. In the npm tarball those links resolve to a file that does not exist. Add `CONTRIBUTING.ja.md` to the copy script and both packages' `files` arrays (and .gitignore) so the shipped Japanese CoC links stay valid, or the links will be broken in node_modules.</comment>
<file context>
@@ -36,7 +36,9 @@
- "README.ja.md"
+ "README.ja.md",
+ "CODE_OF_CONDUCT.md",
+ "CODE_OF_CONDUCT.ja.md"
],
"engines": {
</file context>
- Point every Discord reference (README, README.ja, CONTRIBUTING, CONTRIBUTING.ja) at the discord.arkor.ai vanity URL so the repo no longer mixes two invite links. - Ship CONTRIBUTING.ja.md in both published tarballs so the relative links from the packaged CODE_OF_CONDUCT.ja.md resolve.
|
Code review by qodo was updated up to the latest commit ce19ecf |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce19ecf4fe
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "docs", | ||
| "CONTRIBUTING.md", | ||
| "README.ja.md" | ||
| "CONTRIBUTING.ja.md", |
There was a problem hiding this comment.
When either published package is built and packed, the newly included CONTRIBUTING.ja.md still links relatively to e2e/cli, e2e/studio, and scripts/check-no-em-dash.mts (lines 63–64 and 106), none of which is included in either tarball. Consumers following those links from the packaged guide therefore reach nonexistent paths; make the repository-only links absolute or avoid shipping this guide by using an absolute link from the Japanese Code of Conduct.
Useful? React with 👍 / 👎.
e2e/cli, e2e/studio, and scripts/check-no-em-dash.mts exist only in the repository, so the copies of CONTRIBUTING.md / CONTRIBUTING.ja.md that ship in the published tarballs pointed at nonexistent paths. Link them to github.com instead (README.md and LICENSE.md stay relative: both packages ship their own). Also align the Code of Conduct Discord links with the trailing-slash form main adopted.
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
2 participants
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.
Summary
Adds a bilingual Code of Conduct (
CODE_OF_CONDUCT.md/CODE_OF_CONDUCT.ja.md) at the repo root. GitHub picks up the root file for the community profile automatically.The document has two parts:
Also links the new document from the Code of conduct sections of
CONTRIBUTING.mdandCONTRIBUTING.ja.md, and ships both Code of Conduct files in the publishedarkor/create-arkortarballs (copy-root-files.mjs +files) so the packagedCONTRIBUTING.mdlink resolves.Review feedback applied
CODE_OF_CONDUCT.md(it is the Contributor Covenant's canonical single-sentence pledge, and the Japanese review kept the same structure).Open question
The enforcement section names conduct@arkor.ai as the report address. That alias does not exist yet; we need to either create it or switch the document to another contact before merging.
Checks
pnpm check:no-em-dashandpnpm format:checkpass.Summary by CodeRabbit
New Features
Documentation