Repository navigation
Conversation
Reports arrive without the Windows build, the PIME version, the input method or reproduction steps, so each one costs a retest round-trip before a fix can start. Add one issue form that asks for the fields EasyIME#502 lists, plus where to find the backend and launcher logs, and files the result under `bug`. Generated with assistance from DeepSeek V4.1 Flash.
The form shipped a 2.0.0-beta3 placeholder while upstream already tags 2.0.0-beta4, so the example nudged reporters toward a stale build. Generated with assistance from omp (deepseek-v4.1-flash)
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds one issue form at
.github/ISSUE_TEMPLATE/bug_report.yml. Every future problem report arrives with the data triage already asks for, so a report can become a patch instead of a retest round-trip.The fields are the ones #502 proposed, plus the two log locations the repo already has:
problem(required)expected(required)windows-version,pime-version(required)steps(required)logs(optional)Two additions beyond the issue: the input method and the application, because the backend and TSF layers differ per module and per host (
python_backend.logonly covers the Python backend). The form setslabels: ["bug"], matching the label PCMan had to add by hand across the old backlog on 10-17.One template only, no
config.ymlchooser — the blank-issue path stays available for feature requests.Evidence
git ls-tree -r --name-only origin/master .github/lists onlycopilot-instructions.mdand the two workflows;search/issues?q=repo:EasyIME/PIME+is:pr+ISSUE_TEMPLATEreturns 0, so nothing competes with this.bun -e 'Bun.YAML.parse(await Bun.file(".github/ISSUE_TEMPLATE/bug_report.yml").text())'parses, and the file validates against the SchemaStoregithub-issue-forms.jsonschema withajv-cli(valid, 10 body items, description 65 chars).%LOCALAPPDATA%\PIME\Logs\python_backend.log(python/server.py:34-36),/consoleand/log-file(PIMELauncher/src/main.rs:161-162),version.txt(installer/installer.nsi:294).Merge Danger
Door: two-way — one YAML file; deleting it restores the blank issue form.
Blast Radius: issue creation UX
Generated with assistance from DeepSeek V4.1 Flash.