Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Hacktoberfest 2026: start here

未關閉
  • 哪裡不對？
#73 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
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 分鐘
30 天內合併 PR
122

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

codercops/chatcops 的其他 Issue

查看 codercops/chatcops 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。