[PR #2612] [CLOSED] Update --bug-report.yaml #3934

Closed
opened 2026-03-17 01:30:26 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/hoppscotch/hoppscotch/pull/2612
Author: @nelsonmic
Created: 8/25/2022
Status: Closed

Base: mainHead: patch-1


📝 Commits (1)

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 .github/ISSUE_TEMPLATE/--bug-report.yaml (+4 -0)

📄 Description

Hi there, would you consider using a bug report tool in this bug report tool? It makes sense to have a tool to easily get steps to reproduce, visual proof, and technical logs

Closes #

Description

Checks

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • All the tests have passed

Additional Information


🔄 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/hoppscotch/hoppscotch/pull/2612 **Author:** [@nelsonmic](https://github.com/nelsonmic) **Created:** 8/25/2022 **Status:** ❌ Closed **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`50847fb`](https://github.com/hoppscotch/hoppscotch/commit/50847fb5762c41337a57481c495febd37adc5d67) Update --bug-report.yaml ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/ISSUE_TEMPLATE/--bug-report.yaml` (+4 -0) </details> ### 📄 Description Hi there, would you consider using a bug report tool in this bug report tool? It makes sense to have a tool to easily get steps to reproduce, visual proof, and technical logs <!-- Thanks for creating this pull request 🤗 Please make sure that the pull request is limited to one type (docs, feature, etc.) and keep it as small as possible. You can open multiple prs instead of opening a huge one. --> <!-- If this pull request closes an issue, please mention the issue number below --> Closes # <!-- Issue # here --> ### Description <!-- Add a brief description of the pull request --> <!-- You can also choose to add a list of changes and if they have been completed or not by using the markdown to-do list syntax - [ ] Not Completed - [x] Completed --> ### Checks <!-- Make sure your pull request passes the CI checks and do check the following fields as needed - --> - [x] My pull request adheres to the code style of this project - [ ] My code requires changes to the documentation - [ ] I have updated the documentation as required - [ ] All the tests have passed ### Additional Information <!-- Any additional information like breaking changes, dependencies added, screenshots, comparisons between new and old behavior, etc. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-17 01:30:26 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#3934
No description provided.