cinny/.github/ISSUE_TEMPLATE/feature_request.md at d5cfb663b9cf1ad24e98be39087376bc4954a334

LotusGuild/cinny

Fork 0

Files

T

jaredandClaude Opus 4.8 d5cfb663b9

CI / Build & Quality Checks (push) Successful in 10m54s

Details

CI / Trigger Desktop Build (push) Successful in 5s

Details

chore(issues): point the issue chooser at this repo, not upstream Cinny

The forked-in Cinny issue setup funneled reporters to the upstream project:
- config.yml disabled blank issues and linked to cinnyapp/cinny GitHub
  Discussions
- preapproved.md was Cinny's "do not open an issue, use Discussions"
  template (Gitea has no Discussions anyway)

Replace it with a Lotus setup: enable blank issues, drop the upstream
contact link, and add Bug Report + Feature Request templates. Now
/issues/new/choose offers Lotus templates and files against this repo.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-08-02 20:48:59 -04:00

361 B

Raw Blame History

name, about, title, labels

name	about	title	labels
Feature Request	Suggest an idea or improvement for Lotus Chat		enhancement

What would you like? A clear and concise description of the feature or change.

Why / use case What problem does it solve, or what does it make better?

Alternatives considered Any workarounds or other approaches you've thought about.

361 B Raw Blame History

361 B

Raw Blame History