manishkumar8312 / manishkumar8312/QuickStay

Implement Pull Request & Issue Templates

Open
#51 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
20
Forks
20
PR merge metrics
No merged PRs in 30d

Description

## 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
* **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

```mermaid
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`

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the repository root and whether a .github/ directory already exists. Create .github/pull_request_template.md plus Bug Report and Feature Request issue templates covering the listed details, then verify that all requested files and sections are present and match the proposed contributor workflow.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.