search

dsrvlabs / vatz

Node management integration tools in purpose of maximizing node's uptime for any protocols
https://www.dsrvlabs.com/
GNU General Public License v3.0
30 stars 15 forks source link

Issue to get feedback for registered templates #84

Closed xellos00 closed 2 years ago

xellos00 commented 2 years ago

Checklist

1. Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

with better put br as above.

2. Describe the solution you'd like

A clear and concise description of what you want to happen.

I think this is easier to view on the command

xellos00 commented 2 years ago

This is issue that test using template.

xellos00 commented 2 years ago

1. Bug Report

image

2. CI/CD

image

3. Feature Development

image

4. Feature Request

image

@dsrvlabs/validator give a comment and update template if there's any additional suggestion or comment.

hqueue commented 2 years ago

@xellos00 For templates, LGTM :)

However I have a suggestion related to label which related to #66.

area:ci/cd might be better than type:ci/cd, because CI/CD is not a type but much like area. For example

What do you think of it?

rootwarp commented 2 years ago

LGTM :)

xellos00 commented 2 years ago

@xellos00 For templates, LGTM :)

However I have a suggestion related to label which related to #66.

area:ci/cd might be better than type:ci/cd, because CI/CD is not a type but much like area. For example

  • when we found a bug in C/CI, then we might open an issue with area:ci/cd and type:bug
  • when we open an issue to request new feature of CI/CI, then area:ci/cd and type:feature-request

What do you think of it?

I agree, so let me summarize update for CI/CD

xellos00 commented 2 years ago

As above

meetrick commented 2 years ago

LGTM!!

xellos00 commented 2 years ago

I will close this issue