mirror of
https://github.com/verdaccio/verdaccio.git
synced 2025-02-17 23:45:29 -05:00
chore: new issues report seetings (#1834)
This commit is contained in:
parent
530018895c
commit
e8e94182a4
5 changed files with 60 additions and 95 deletions
66
.github/ISSUE_TEMPLATE/Bug_report.md
vendored
66
.github/ISSUE_TEMPLATE/Bug_report.md
vendored
|
@ -1,66 +0,0 @@
|
|||
---
|
||||
name: Bug report
|
||||
about: Create a report to help us improve
|
||||
---
|
||||
|
||||
<!--
|
||||
Hi folk, please read carefully the following points, all this information is what you need to share and make the process efficient
|
||||
so everybody can understand your issue, please notice if you don't fill any of this points our friendly boot will remind you to do it or
|
||||
close automatically the issue. Removing the sections you consider are irrelevant for your issue is totally ok.
|
||||
|
||||
If you have questions, you might rather join use over Discord https://chat.verdaccio.org
|
||||
|
||||
As reminder, we have code of conduct all of us we must follow https://github.com/verdaccio/verdaccio/blob/master/CODE_OF_CONDUCT.md
|
||||
-->
|
||||
|
||||
**Describe the bug**
|
||||
<!-- A clear and concise description of what the bug is. -->
|
||||
|
||||
**To Reproduce**
|
||||
<!-- How to reproduce the issue -->
|
||||
|
||||
Steps to reproduce the behavior:
|
||||
1. Go to '...'
|
||||
2. Click on '....'
|
||||
3. Scroll down to '....'
|
||||
4. See error
|
||||
|
||||
**Expected behavior**
|
||||
<!-- A clear and concise description of what you expected to happen. -->
|
||||
|
||||
**Screenshots**
|
||||
If applicable, add screenshots to help explain your problem.
|
||||
|
||||
**Docker || Kubernetes (please complete the following information):**
|
||||
- Docker verdaccio tag: [e.g. verdaccio:4.x]
|
||||
- Docker commands [e.g. docker pull ...]
|
||||
- Docker Version [e.g. v18.05.0-ce-rc1]
|
||||
|
||||
**Configuration File (cat ~/.config/verdaccio/config.yaml)**
|
||||
|
||||
<!-- Please be careful do not leak any sensitive information, remove tokens -->
|
||||
|
||||
**Environment information**
|
||||
|
||||
<!--
|
||||
Please paste the results of `verdaccio --info` here (only if you are using >4.0.0).
|
||||
Share, Node.js, node package manager used (npm, yarn or pnpm) and the version.
|
||||
The verdaccio version is really important, run `verdaccio --version` if you don't know it.
|
||||
-->
|
||||
|
||||
**Debugging output**
|
||||
<!-- If you are contributing and need to share internal stuff, here some useful commands to get more verbose output -->
|
||||
|
||||
- `$ NODE_DEBUG=request verdaccio` display request calls (verdaccio <--> uplinks)
|
||||
- `$ DEBUG=express:* verdaccio` enable extreme verdaccio debug mode (verdaccio api)
|
||||
- `$ npm -ddd` prints:
|
||||
- `$ npm config get registry` prints:
|
||||
|
||||
**Additional context**
|
||||
|
||||
<!--
|
||||
|
||||
If there is something else to share, screenshots, log files, or link references to other tickets.
|
||||
IMPORTANT: please do not attach log files, rather copy the content so is indexable for future search.
|
||||
-->
|
||||
|
41
.github/ISSUE_TEMPLATE/bug.md
vendored
Normal file
41
.github/ISSUE_TEMPLATE/bug.md
vendored
Normal file
|
@ -0,0 +1,41 @@
|
|||
---
|
||||
name: Bug report 🐛
|
||||
about: A feature is not working as is expected, I want to report a bug
|
||||
labels: "issue: bug"
|
||||
---
|
||||
|
||||
**Describe the bug**
|
||||
<!-- A clear and concise description of what the bug is. -->
|
||||
|
||||
**To Reproduce**
|
||||
<!-- IMPORTANT:
|
||||
- How to reproduce the issue
|
||||
- Steps to reproduce the issue
|
||||
|
||||
Be aware, the lack of reproducible steps the issue might cause your ticket to be closed.
|
||||
-->
|
||||
|
||||
**Expected behavior**
|
||||
<!-- A clear and concise description of what you expected to happen. -->
|
||||
|
||||
**Screenshots**
|
||||
<!-- If applicable, add screenshots to help explain your problem. -->
|
||||
|
||||
**Configuration File (cat ~/.config/verdaccio/config.yaml)**
|
||||
|
||||
<!-- Please be careful do not leak any sensitive information, remove tokens -->
|
||||
|
||||
**Environment information**
|
||||
<!-- Please paste the results of running `verdaccio --info` -->
|
||||
|
||||
**Debugging output**
|
||||
- `$ NODE_DEBUG=request verdaccio` display request calls (verdaccio <--> uplinks)
|
||||
- `$ DEBUG=express:* verdaccio` enable extreme verdaccio debug mode (verdaccio api)
|
||||
- `$ npm -ddd` prints:
|
||||
- `$ npm config get registry` prints:
|
||||
|
||||
<!--
|
||||
|
||||
IMPORTANT: please do not attach external files, all content should be visible from any device.
|
||||
-->
|
||||
|
14
.github/ISSUE_TEMPLATE/config.yml
vendored
Normal file
14
.github/ISSUE_TEMPLATE/config.yml
vendored
Normal file
|
@ -0,0 +1,14 @@
|
|||
blank_issues_enabled: false
|
||||
contact_links:
|
||||
- name: Question 🤷🏻♂️
|
||||
url: https://stackoverflow.com/questions/tagged/verdaccio
|
||||
about: We encorage you to open new questions on Stackoverflow
|
||||
- name: Security Report 🛡
|
||||
url: https://github.com/verdaccio/verdaccio/security/policy
|
||||
about: I want to report a security vulnerability
|
||||
- name: Chat 🏘
|
||||
url: http://chat.verdaccio.org
|
||||
about: For a quick question you should do it through our community chat
|
||||
- name: User Interface Report 👩🏼🎨👨🏼🎨
|
||||
url: https://github.com/verdaccio/ui/issues/new/choose
|
||||
about: Any report related with the User Interface should be posted in another repository
|
|
@ -1,6 +1,9 @@
|
|||
---
|
||||
name: Feature request
|
||||
about: Suggest an idea for this project
|
||||
name: "Feature Request 🔮"
|
||||
about: You want a feature request.
|
||||
title: ""
|
||||
labels: "topic: feature request"
|
||||
assignees: ""
|
||||
---
|
||||
|
||||
<!--
|
27
.github/pull_request_template.md
vendored
27
.github/pull_request_template.md
vendored
|
@ -1,27 +0,0 @@
|
|||
<!--
|
||||
|
||||
Before Pull Request check whether your commits follow this convention
|
||||
|
||||
https://github.com/verdaccio/verdaccio/blob/master/CONTRIBUTING.md#git-commit-guidelines
|
||||
|
||||
* If your PR fix an issue don't forget to update the unit test and documentation in /docs folder
|
||||
* If your PR delivers a new feature, please, provide examples and why such feature should be considered.
|
||||
* Document your changes /docs
|
||||
* Add unit test
|
||||
* Follow the commit guidelines in order to get a quick approval
|
||||
|
||||
Pick one/multiple type, if none apply please suggest one, we might be included it by default
|
||||
|
||||
eg: bug / feature / documentation / unit test / build
|
||||
|
||||
-->
|
||||
**Type:**
|
||||
|
||||
The following has been addressed in the PR:
|
||||
|
||||
* There is a related issue?
|
||||
* Unit or Functional tests are included in the PR
|
||||
|
||||
**Description:**
|
||||
|
||||
<!-- Resolves #??? -->
|
Loading…
Add table
Reference in a new issue