[PR #1379] [MERGED] feat(other): update issue templates #1468

New issue

Closed

opened 2026-02-25 21:38:22 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 21:38:22 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/cypht-org/cypht/pull/1379
Author: @ulfgebhardt
Created: 11/22/2024
Status: ✅ Merged
Merged: 11/22/2024
Merged by: @marclaporte

Base: master ← Head: issue-templates

📝 Commits (1)

3490a9b update issue templates

📊 Changes

12 files changed (+162 additions, -62 deletions)

View changed files

📝 .github/ISSUE_TEMPLATE.md (+5 -5)
➕ .github/ISSUE_TEMPLATE/bug.md (+16 -0)
➖ .github/ISSUE_TEMPLATE/bug_report.md (+0 -20)
➕ .github/ISSUE_TEMPLATE/devops.md (+10 -0)
➕ .github/ISSUE_TEMPLATE/epic.md (+13 -0)
📝 .github/ISSUE_TEMPLATE/feature.md (+5 -6)
📝 .github/ISSUE_TEMPLATE/question.md (+7 -1)
➕ .github/ISSUE_TEMPLATE/refactor.md (+10 -0)
➕ .github/ISSUE_TEMPLATE/release.md (+13 -0)
➖ .github/ISSUE_TEMPLATE/suggestion.md (+0 -9)
📝 .github/PULL_REQUEST_TEMPLATE.md (+6 -21)
➕ .github/workflows/test.lint.pr.yml (+77 -0)

📄 Description

Pullrequest

Update issue templates

Motivation

Since I am invested in testing cypht lately, i figured the issue templates are now 6 years old and have evolved on my end a bit.
So here is an update.

What has changed?

Templates are more simple so developers are actually tempted not to just replace the whole contents but fill out the data (see pullrequest template especially)
The title of a new issue will be preset. This results in well organized issue lists with visual cues what type of issue it is with no effort for the issue creator
There is new types of issues: epic, devops, refactor, release
The suggestion type is gone
There is a new workflow which checks if a PR title is well formed. This needs some getting used to, but results in a nice changelog based on PR titles.

You can explore how things would look like here: https://github.com/ulfgebhardt/issue-templates

Example of a well formed changelog generated by https://github.com/CookPete/auto-changelog

Issues

None

Todo

Decided if all types should be part of the repo - is epic a thing here? Is devops needed?
Do you want the PR title workflow?
Create all labels for the types decided for - see https://github.com/ulfgebhardt/issue-templates?tab=readme-ov-file#labels

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/cypht-org/cypht/pull/1379 **Author:** [@ulfgebhardt](https://github.com/ulfgebhardt) **Created:** 11/22/2024 **Status:** ✅ Merged **Merged:** 11/22/2024 **Merged by:** [@marclaporte](https://github.com/marclaporte) **Base:** `master` ← **Head:** `issue-templates` --- ### 📝 Commits (1) - [`3490a9b`](https://github.com/cypht-org/cypht/commit/3490a9bde9a6d6722ec8c23dd19cd2d04118c219) update issue templates ### 📊 Changes **12 files changed** (+162 additions, -62 deletions) <details> <summary>View changed files</summary> 📝 `.github/ISSUE_TEMPLATE.md` (+5 -5) ➕ `.github/ISSUE_TEMPLATE/bug.md` (+16 -0) ➖ `.github/ISSUE_TEMPLATE/bug_report.md` (+0 -20) ➕ `.github/ISSUE_TEMPLATE/devops.md` (+10 -0) ➕ `.github/ISSUE_TEMPLATE/epic.md` (+13 -0) 📝 `.github/ISSUE_TEMPLATE/feature.md` (+5 -6) 📝 `.github/ISSUE_TEMPLATE/question.md` (+7 -1) ➕ `.github/ISSUE_TEMPLATE/refactor.md` (+10 -0) ➕ `.github/ISSUE_TEMPLATE/release.md` (+13 -0) ➖ `.github/ISSUE_TEMPLATE/suggestion.md` (+0 -9) 📝 `.github/PULL_REQUEST_TEMPLATE.md` (+6 -21) ➕ `.github/workflows/test.lint.pr.yml` (+77 -0) </details> ### 📄 Description ## Pullrequest  Update issue templates ![image](https://github.com/user-attachments/assets/acaf9246-35f8-43f5-84df-cfe66820012f) ### Motivation Since I am invested in testing cypht lately, i figured the issue templates are now 6 years old and have evolved on my end a bit. So here is an update. ### What has changed? - Templates are more simple so developers are actually tempted not to just replace the whole contents but fill out the data (see pullrequest template especially) - The title of a new issue will be preset. This results in well organized issue lists with visual cues what type of issue it is with no effort for the issue creator - There is new types of issues: epic, devops, refactor, release - The suggestion type is gone - There is a new workflow which checks if a PR title is well formed. This needs some getting used to, but results in a nice changelog based on PR titles. You can explore how things would look like here: https://github.com/ulfgebhardt/issue-templates Example of a well formed changelog generated by https://github.com/CookPete/auto-changelog ![image](https://github.com/user-attachments/assets/8f696cf6-e6cb-451e-b3bc-9d48d9f93e3f) ### Issues  - [X] None ### Todo  - [x] Decided if all types should be part of the repo - is epic a thing here? Is devops needed? - [ ] Do you want the PR title workflow? - [x] Create all labels for the types decided for - see https://github.com/ulfgebhardt/issue-templates?tab=readme-ov-file#labels --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>