docs: add Issue Form templates for the Tabularis migration flow - #62
Merged
Conversation
Add three GitHub Issue Form templates under .github/ISSUE_TEMPLATE/ that the Tabularis builtin-to-plugin migration flow pre-fills via query params keyed on each form element's id: - migration-failure.yml: filed when switching a connection from the builtin postgres driver to this plugin fails (failure_mode dropdown, version/OS/error fields, labels: migration) - capability-gap.yml: filed when a connection uses a builtin-only feature the plugin doesn't yet cover (labels: capability-gap) - bug_report.yml: general bug report from the standing 'Report a plugin issue' link in Settings (labels: bug) Verified against the official schemastore Issue Forms JSON schema (all three valid), with unique underscore-legal ids per form, markdown elements carrying no id, and the referenced labels (migration, capability-gap, bug) all present on the repo. Closes #56
aesslinger
added a commit
that referenced
this pull request
Sep 4, 2026
Ships the configurable pool-size feature (PR #63, porting tabularis#681) and three dependency bumps (PRs #55/#59/#60), plus the migration Issue Form templates (PR #62). Headline change: a poolMaxSize driver setting (default 10, clamped to 1-64, parsed from u64/i64/string, zero/invalid -> default) received via the initialize RPC. Restores pool-size parity with the built-in driver (build_pool previously never set max_size, so deadpool defaulted to cpu×2 — up to ~32 on a 16-thread machine — vs. the built-in's pinned 10). Verified: .tabularium re-validated as valid JSON with version matching the upcoming v1.0.0-beta.10 tag; cargo build/test (133 unit + 8 live-DB against the local pg-tabularis-test container)/clippy/fmt all pass; the release binary returns a valid initialize JSON-RPC response.
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
1 participant
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 three GitHub Issue Form templates under
.github/ISSUE_TEMPLATE/that the Tabularis builtin-to-plugin migration flow pre-fills via query params keyed on each form element'sid(per the design in TabularisDB/tabularis#685, issue #56):migration-failure.yml— filed when switching a connection from the builtinpostgresdriver to this plugin fails. Failure-mode dropdown (process vs. connection), version/OS/error fields. Labels:migrationcapability-gap.yml— filed when a connection uses a builtin-only feature the plugin doesn't yet cover. Labels:capability-gapbug_report.yml— general bug report from the standing "Report a plugin issue" link in Settings. Labels:bugAlso created the
migrationandcapability-gaplabels on the repo (bugalready existed), so each template'slabels:frontmatter auto-applies them going forward.Part 2 of #56 (the builtin-vs-plugin capability diff) needs no separate work here — it already runs as part of every plugin release; gaps it turns up should be filed with the new
capability-gaptemplate.Verification
All three templates validated before commit:
json.schemastore.org/github-issue-forms.json) —npx ajv-cli validate→ valid for all threeids use only^[a-zA-Z0-9_-]+$(underscores allowed per schema pattern + GitHub form-schema docs)ids unique within each form;markdownelements carry noid(per schema/docs)typeis in the allowed set (input/textarea/dropdown/markdown); the dropdown'soptionskey is presentidthe app targets (failure_mode,plugin_version,app_version,os,error,feature, …) exists in its template, so?template=…&id=valuequery params resolve correctlymigration,capability-gap,bug) exist on the repoContent is verbatim from #56.
Versioning
docs:type — no release impact per the README's type→bump table. Labeledprerelease:beta(current channel) to satisfy CI's requiredprerelease:*label; CI's version suggestion will correctly resolve to no change.Closes #56.