Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Hacktoberfest 2026: start here

オープン
#73 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
1/5
見積もり時間
1時間未満
初心者へのやさしさ
35/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript
領域
documentation

調査の方向性

This is a contributor guide, not a request for a specific change. Read CONTRIBUTING.md for workspace setup and contribution steps; use the linked issue lists to find scoped work, and ask in this thread if anything is unclear. Done means following the guide to choose an agreed issue and submit a PR under the stated process.

索引モデルが issue の本文から書いたものです。

説明

hacktoberfest

Welcome! If you're here for Hacktoberfest, this is the quickest way in. ChatCops is an embeddable chatbot widget with a server package and a docs site.

Find something to work on

  • Unassigned good first issues are small and well scoped. Good for a first PR.
  • Unassigned help wanted issues are a bit bigger.
  • New this week: groundwork for the next release, as small self-contained pieces. Security helpers for the server (#228, #229, #230, #231, #232), tool call ids (#227), a cross-origin browser test (#233), AI labels on bubbles (#234), a smaller widget bundle (#235), a docs fix (#236), and pieces of the new stream format and provider setup (#238, #239, #240, #241, #242). Bigger ones for repeat contributors: a rate limiter and analytics on the new storage interfaces (#245, #246), and the SQLite, Redis and Cloudflare stores (#247, #248, #249). Some have a "merge by" date because I start rewriting those files after it.

How it works

  1. Comment on the issue you want. I'll assign it to you, usually within a day. Please don't start on one that's assigned to someone else.
  2. One issue at a time. Once you've had 3 PRs merged with us, you can hold two.
  3. Branch off dev, open your PR against dev, and put Closes #<issue number> in the description. The PR has to be opened here in codercops/chatcops: one merged inside your own fork never reaches us, so it doesn't count.
  4. If there's no PR or update 5 days after you're assigned, I'll free the issue up for someone else. Comment if you need more time.

Setup
This is a pnpm workspace (npm won't work), and you need to run pnpm -r build before pnpm test. Both are covered in CONTRIBUTING.md. See CONTRIBUTING.md.

What counts
PRs count for Hacktoberfest once they're merged or labeled hacktoberfest-accepted. PRs that aren't linked to an issue, only reformat code, or change things nobody asked for get closed, and spam gets the spam label. Have an idea that isn't an issue yet? Open one first so we can agree on it.

AI tools and spam
AI tools are fine, but say so in the PR (the template has an "AI assistance" line) and be ready to explain every line. Untested generated code, a fix split into several PRs, and PRs for issues that aren't assigned to you are treated as spam. Two spam PRs and you won't be assigned more issues this month, and you're out of the goodies. The full rules are in CONTRIBUTING.md.

Goodies
CODERCOPS October 2026 is our own contributor program for this month. The top 5 contributors get a CODERCOPS T-shirt and stickers. You need at least 5 merged PRs labeled hacktoberfest-accepted across chatcops, ogcops, toolbelt and discord-bot, merged between Oct 1 and Oct 31 (UTC). A review can take a day, and changes add another round, so open your PR by Oct 28 to be safe. We still review PRs opened later, but can't promise they get merged by the 31st. Ties go to whoever got there first. The live leaderboard shows where everyone stands, and everyone on it gets a card to share.

These goodies come from CODERCOPS through our own open source program. They're separate from Hacktoberfest, so anything Hacktoberfest itself gives out is a different thing with its own rules. Only PRs for issues that were assigned to you count, and what counts is the maintainers' call.

Questions about anything? Ask right here, or come chat with other contributors on Discord. Claims still happen here on GitHub.

主要言語
TypeScript
スター
13
フォーク
7
平均マージ
4時間 11分
マージ済み PR(30日)
122

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

codercops/chatcops のほかの issue

codercops/chatcops の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。