Meta-issue: Automatically closing reports for bugs that you haven't fixed yet is a terrible policy

Open
#1,105 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
tooling

Research direction

No files, tests, or entry points are named. Start by reviewing the repository's stale-bot configuration and the referenced report #1044; done would require an agreed policy for requesting details and closing unresolved reports.

Written by the indexing model from the issue text.

Description

product

Your 'stale' bot appears to comment on reports that have been inactive for 6 months asking for more details (regardless of how many have been provided), then closes the report (after only 1 hour!). This results in legitimate bugs like #1044 being closed without a fix. I'm sure you're aware that bugs make your product less attractive to potential customers like me, and closing reports without fixing the issue makes you look unprofessional and motivates me to look for an alternative that is better managed.

Dominant language
Java
Stars
242
Forks
116
No merged PRs in 30d

Contributor guide

Open the 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 mapbox/mapbox-plugins-android

All issues in mapbox/mapbox-plugins-android

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.