You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The repository currently lacks a standardized way for contributors to describe their changes. This leads to PRs that are difficult to review because they lack context, testing details, or links to related issues.
Proposed Solution
Create a .github/ directory and implement standard templates to streamline the contribution process.
Requirements
PR Template: Create .github/pull_request_template.md including:
* Description of changes.
* Type of change (feature, bug fix, docs).
* Checkbox for testing performed.
* Links to relevant issues (e.g., Closes #123).
Issue Templates: Add templates for Bug Reports and Feature Requests to ensure users provide environment details and clear reproduction steps.
Expected Workflow
graph LR
A[Contributor] -->|Opens PR| B{PR Template Auto-fills}
B --> C[Contributor fills details]
C --> D[Maintainer Review]
D -->|Consistent Info| E[Merge]
Problem
The repository currently lacks a standardized way for contributors to describe their changes. This leads to PRs that are difficult to review because they lack context, testing details, or links to related issues.
Proposed Solution
Create a
.github/directory and implement standard templates to streamline the contribution process.Requirements
.github/pull_request_template.mdincluding:* Description of changes.
* Type of change (feature, bug fix, docs).
* Checkbox for testing performed.
* Links to relevant issues (e.g., Closes #123).
Expected Workflow
graph LR A[Contributor] -->|Opens PR| B{PR Template Auto-fills} B --> C[Contributor fills details] C --> D[Maintainer Review] D -->|Consistent Info| E[Merge]Labels:
documentation,DSCWOC'26,DSCWOC