Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

"Report an Issue" menu item creates blank issues that are auto-closed by the template bot

Open Beginner friendly
  • Is something wrong?
#269 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@noah-qin is already working on this.

Since Oct 25, 2026.

  • #293 by @noah-qin — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, swift
Domain
desktop

Research direction

Find where the Help menu's "Report an Issue" item builds its URL, which currently sends title and body query parameters to issues/new. Check the behaviour against the issues/new/choose chooser and the bug.yml and feature.yml templates named in the report. Done when the menu item opens the chooser or a specific template, so a submitted report is not auto-closed by the template bot.

Written by the indexing model from the issue text.

Description

Before submitting
  • I have searched the issues and pull requests for duplicates.
  • I am reporting a specific problem with BrewUI and have described how to reproduce it, or the circumstances of an intermittent failure.
What happened?

The app's "Report an Issue" menu item opens github.com/Homebrew/BrewUI/issues/new?title=...&body=..., which creates a blank issue. A GitHub Actions workflow then auto-closes the issue within seconds because it doesn't contain the required template headings. The user gets no warning that their report will be rejected thus making it a very frustrating experience.

Examples:

Also note the PS from #197, so others have the same problem:

PS - This is the re-edited version so that it gets in front of your eyeballs. My original issue was pasted into a window which was opened by the "Report and issue ..." button in the Help menu. If you require the sections that i've now had to paste in, why don't you provide them in the first place when the issue window is open?

Homebrew configuration: NA, github issue

Expected behaviour

The "Report an Issue" menu item should open the template chooser (issues/new/choose) or link directly to the appropriate template form (issues/new?template=bug.yml or issues/new?template=feature.yml) so the user's issue isn't immediately auto-closed.

Steps to reproduce
  1. Open BrewUI
  2. Use the "Report an Issue" menu item (or Help > Report an Issue)
  3. Write an issue in the form that opens
  4. Submit
    5. Issue is closed by github-actions bot within seconds
App version and build

0.6.0 (1201)

How was the app installed?

Homebrew cask

macOS version and build

Tahoe 26.7.1

Mac processor

Apple silicon

Homebrew configuration
sh
HOMEBREW_VERSION: 7.0.9-102-gc18602a
ORIGIN: https://github.com/Homebrew/brew
HEAD: c18602a1861ae7df32627ceaa996eb2448eccb9a
Last commit: 75 minutes ago
Branch: main
Core tap HEAD: e2396e85fc2d67938e22c85b52b2b1e2b6c6473f
Core tap last commit: 2 days ago
Core cask tap HEAD: af16d526785ebdc59563777d8901b0598128c8c8
Core cask tap last commit: 2 days ago
HOMEBREW_PREFIX: /Users/mitch.scobell/homebrew
HOMEBREW_REPOSITORY: /Users/mitch.scobell/homebrew
HOMEBREW_CELLAR: /Users/mitch.scobell/homebrew/Cellar
HOMEBREW_CASK_OPTS: ["--appdir=~/Applications"]
Homebrew Ruby: 4.0.7 => /Users/mitch.scobell/homebrew/Library/Homebrew/vendor/portable-ruby/4.0.7_1/bin/ruby
CPU: deca-core 64-bit arm_firestorm_icestorm
Clang: 21.0.0 build 2100
Git: 2.52.0 => /Users/mitch.scobell/homebrew/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 26.7.1-arm64
CLT: 26.6.0.0.1781586589
Xcode: 27.0
Metal Toolchain: N/A
Rosetta 2: false
Logs, screenshots and crash reports

No response

Additional context

https://github.com/Homebrew/BrewUI/issues/197#issuecomment-5679053349
and
https://github.com/Homebrew/BrewUI/issues/268#issuecomment-6171390309

Dominant language
Swift
Stars
2.7k
Forks
87
Avg merge
2d 13h
Merged PRs (30d)
11

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Homebrew/BrewUI

All issues in Homebrew/BrewUI

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.