Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Stale bot marks Help Wanted / Good First Issue issues as abandoned

未关闭 适合新手
#7,262 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 4 天内回复

@KoushikSagarr 已经在做这个了。

开始于 2026年10月30日。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github-actions, yaml
领域
ci-cd

调研方向

从 .github/workflows/stale.yml 开始,检查 actions/stale 的设置。添加建议的标签豁免项和更友好的消息,然后在 PR 中记录一次性清理 no-issue-activity 标签的操作。Issue 建议在 fork 上使用 debug-only: true 检查配置;豁免标签已配置、消息已更新且清理操作已记录,即表示完成。

由索引模型根据 Issue 内容生成。

描述

github_actions Good First Issue

Problem

.github/workflows/stale.yml posts "This issue has been open without changes for a long time! What's up?" and labels no-issue-activity on 33 of our 41 open issues, including Help Wanted, Good First Issue, and 🗺️ Epic issues that are waiting for a contributor, not for the reporter. For a new contributor browsing issues, almost everything looks abandoned, and the comment asks them "what's up?".

Meanwhile, real contributor questions go unanswered. Two people asked to be assigned in October and waited weeks (#7241, #7106).

Proposal

In .github/workflows/stale.yml (actions/stale):

  • Add exempt-issue-labels: "Help Wanted,Good First Issue,🗺️ Epic,Stakeholder-Feature" and exempt-all-issue-assignees: false (keep assigned issues in scope, since those are the ones that actually go stale)
  • Friendlier message, e.g. "This issue hasn't had activity in a while. If you're working on it, a quick update helps. If you'd like to pick it up, comment and a maintainer will assign you."
  • Remove the no-issue-activity label from currently exempt issues (one-off gh loop, documented in the PR)

Notes for contributors

This is a small YAML change and a good first issue. You can test the config with debug-only: true on a fork. (Maintainers: merging needs a token with the workflow scope.)

主要语言
Ruby
星标
382
派生
547
平均合并
7 天 21 小时
30 天内合并 PR
28

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

rubyforgood/casa 的其他 Issue

查看 rubyforgood/casa 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。