Skip to content

Commit f1beb0c

Browse files
committed
init: pr template
1 parent 4a055e2 commit f1beb0c

File tree

5 files changed

+76
-44
lines changed

5 files changed

+76
-44
lines changed

.github/ISSUE_TEMPLATE/bug---context-of-the-bug--.md

Lines changed: 0 additions & 27 deletions
This file was deleted.
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
name: 'Bug Report Template'
3+
about: Report a bug to help us improve
4+
title: 'bug: <context of the bug>'
5+
labels: bug
6+
assignees: ''
7+
8+
---
9+
10+
# Bug Report
11+
12+
**Describe the bug**
13+
A clear and concise description of what the bug is.
14+
15+
**To Reproduce**
16+
Steps to reproduce the behavior:
17+
1. Go to '...'
18+
2. Click on '....'
19+
3. Scroll down to '....'
20+
4. See error
21+
22+
**Expected behavior**
23+
What you expected to happen.
24+
25+
**Screenshots (optional)**
26+
Add screenshots if helpful.
27+
28+
**Additional context (optional)**
29+
Anything else relevant.

.github/ISSUE_TEMPLATE/feature---feature-request-.md

Lines changed: 0 additions & 17 deletions
This file was deleted.
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
name: 'Feature Request'
3+
about: Suggest an idea or enhancement
4+
title: 'feature: <feature request>'
5+
labels: enhancement
6+
assignees: ''
7+
8+
---
9+
10+
# Feature Request
11+
12+
**Describe the feature you'd like**
13+
A short description of the desired feature.
14+
15+
**Why is this feature important?**
16+
Explain the benefit or use case. Is your feature request related to a problem?
17+
18+
**Describe alternatives you've considered**
19+
List any alternative solutions or workarounds considered.
20+
21+
**Additional context**
22+
Add any other details or mockups here.

.github/pull_request_template.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# Pull Request
2+
3+
## Description
4+
5+
Briefly describe the changes introduced in this PR.
6+
7+
**Related Issues**
8+
Link any related issues (e.g., `Issue #12`).
9+
10+
## Type of change
11+
- [ ] Bug fix (non-breaking change which fixes an issue)
12+
- [ ] New feature (non-breaking change which adds functionality)
13+
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
14+
- [ ] This change requires a documentation update
15+
- [ ] Housekeeping
16+
17+
## Checklist:
18+
- [ ] My code follows the [ruff code style](http://stellarium.org/doc/head/codingStyle.html) of this project.
19+
- [ ] I have performed a self-review of my own code
20+
- [ ] I have commented my code, particularly in hard-to-understand areas
21+
- [ ] I have made corresponding changes to the documentation (if applicable)
22+
- [ ] I have added tests that prove my fix is effective or that my feature works
23+
- [ ] New and existing unit tests pass locally with my changes
24+
- [ ] `poetry run pytest` - all tests passed
25+
- [ ] `poetry run ruff check` - no linting errors

0 commit comments

Comments
 (0)