chore: add PR and issue templates#2
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Adds standardized GitHub contribution templates to pdfdebug so incoming PRs and issues are consistently structured and better triaged.
Changes:
- Added a repository PR template covering description, testing, risk, and checklist items.
- Added structured GitHub Issue Forms for bug reports and feature requests.
- Added Issue Template configuration enabling blank issues and routing security reports to
security@unidoc.io.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/pull_request_template.md | Introduces a consistent PR submission structure and checklist (incl. dev vs master guidance). |
| .github/ISSUE_TEMPLATE/bug_report.yml | Adds a structured bug report form with repro, expected/actual, surface selection, and version capture. |
| .github/ISSUE_TEMPLATE/feature_request.yml | Adds a structured feature request form capturing motivation, solution, and alternatives. |
| .github/ISSUE_TEMPLATE/config.yml | Enables blank issues and adds a security contact link to email security reports. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
unidoc-anom
approved these changes
Jul 14, 2026
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.
Description and links
pdfdebug had no PR template and no structured issue templates, unlike newer UniDoc repos (e.g. isms). This adds both so contributions follow a consistent shape.
Technical changes
.github/pull_request_template.md, adapted from unipdf-src's internal template with JIRA links and the User-Guide-doc-gate dropped (don't apply to a small public repo)..github/ISSUE_TEMPLATE/bug_report.ymlandfeature_request.ymlas GitHub issue forms, scoped to pdfdebug's actual surfaces (GUI/CLI/pdfcore/build) rather than copied verbatim from another repo..github/ISSUE_TEMPLATE/config.ymlto keep the blank-issue option and redirect security reports to security@unidoc.io, matching what CONTRIBUTING.md already documents.Considerations
Went with GitHub's newer YAML issue-forms format (structured fields) rather than unipdf/unioffice's plain markdown templates, since it's the more current convention internally (isms) and gives better-triaged bug reports. unipdf/unioffice remain on the older style for now — a possible follow-up if we want the public repos consistent.
How was this tested?
Templates-only change, no code affected.
What could go wrong?
Low risk — these only affect the GitHub UI forms shown when opening a new issue/PR, no runtime behavior.
Screenshots/videos (if appropriate)
N/A — will confirm the forms render correctly by opening a test issue/PR in the GitHub UI after merge.
Checklist
devbranch, notmaster