No star, No fix
A GitHub project that automatically closes issues from users who haven’t starred the repo is provoking debate over ethics, practicality, and platform policy. Critics argue that conditioning bug reports and feature requests on “internet points” corrupts the meaning of stars, deters valuable reports (including security issues), and may violate GitHub’s rules on inauthentic activity. Supporters counter that maintainers are unpaid, overwhelmed, and entitled to add friction or request minimal gestures of support, even if it skews public popularity signals.
Policy and Rule Compliance
- Some argue the “star-gated” bot (closing issues until the reporter stars the repo) likely violates GitHub’s rules on automated starring / “coordinated inauthentic activity.”
- Others counter that it’s not clearly against the rules because: it’s user-initiated, requires explicit consent, isn’t auto-starring, and repo owners have no obligation to provide support.
- A few note that, regardless of current rules, such schemes should be disallowed because they distort platform signals.
Meaning and Integrity of Stars
- Many see stars as personal bookmarks or genuine endorsements; conditioning issue handling on stars is viewed as corrupting that signal.
- Critics say this inflates star counts based on annoyance or necessity (e.g., breaking dependencies), not admiration or popularity.
- Supporters claim bug reporters are already “interested users,” so requiring a star actually aligns stars more closely with real usage.
Ethics, Power Dynamics, and “Extortion” Framing
- Several commenters call the practice sleazy, petty, or “extortion-like”: “I won’t even consider your issue unless you publicly like me.”
- Concerns include: emotional manipulation, reputational red flags for organizations evaluating the project, and discouraging valuable drive‑by reports (including potential security issues).
- Others argue maintainers can set arbitrary boundaries for free labor, and asking for a star is minimal payment for attention.
Maintainer Burden and Noise Reduction
- Defenders emphasize maintainer overload: issue queues are flooded, and mild friction (like a star) can filter low‑effort reports.
- Critics reply that this doesn’t distinguish good from bad reports and blocks even high‑quality offers to contribute code.
Practical Consequences and Edge Cases
- Commenters highlight use cases where people file issues without “liking” the project: automated tools, security research, transitive dependencies, or evaluation of multiple options.
- Some would star briefly then unstar once their issue is handled; others refuse on principle, preferring donations or bounties.
- Several note that if this practice spreads, it triggers a “star inflation war,” degrading stars much like manipulated reviews on marketplaces.