graphql-engine
graphql-engine copied to clipboard
doc(ISSUE_TEMPLATE): use `.yml` format instead of `.md` (close #9062)
Description
In this PR, I converted issue templates from .md
to .yml
.
Changelog
No changes which user affected.
Short Changelog
use yml format on issue templates
Long Changelog
define issue form with YAML issue templates
Related Issues
https://github.com/hasura/graphql-engine/issues/9062
Steps to test and verify
You can check the content and design of issue form from below links:
- Bug report: https://github.com/progfay/hasura-graphql-engine/issues/new?assignees=&labels=k%2Fbug&template=01_bug_report.yml&title=%5BBug%5D%3A+
- Feature request: https://github.com/progfay/hasura-graphql-engine/issues/new?assignees=&labels=k%2Fenhancement&template=02_feature_request.yml&title=%5BRequest%5D%3A+
Catalog upgrade
Does this PR change Hasura Catalog version?
- [x] No
- [ ] Yes
- [ ] Updated docs with SQL for downgrading the catalog
Metadata
Does this PR add a new Metadata feature?
- [x] No
- [ ] Yes
- Does
run_sql
auto manages the new metadata through schema diffing?- [ ] Yes
- [ ] Not required
- Does
run_sql
auto manages the definitions of metadata on renaming?- [ ] Yes
- [ ] Not required
- Does
export_metadata
/replace_metadata
supports the new metadata added?- [ ] Yes
- [ ] Not required
- Does
GraphQL
- [x] No new GraphQL schema is generated
- [ ] New GraphQL schema is being generated:
- [ ] New types and typenames are correlated
Breaking changes
-
[x] No Breaking changes
-
[ ] There are breaking changes:
-
Metadata API
Existing
query
types:- [ ] Modify
args
payload which is not backward compatible - [ ] Behavioural change of the API
- [ ] Change in response
JSON
schema - [ ] Change in error code
- [ ] Modify
-
GraphQL API
Schema Generation:
- [ ] Change in any
NamedType
- [ ] Change in table field names
Schema Resolve:-
- [ ] Change in treatment of
null
value for any input fields
- [ ] Change in any
-
Logging
- [ ] Log
JSON
schema has changed - [ ] Log
type
names have changed
- [ ] Log
-
Beep boop! :robot:
Hey @progfay, thanks for your PR!
One of my human friends will review this PR and get back to you as soon as possible.
Stay awesome! :sunglasses:
Hello, @IAmTamal and @adas98012.
I converted Issue Templates from .md
to .yml
, please review my PR.
Thanks!
Hello, @IAmTamal and @adas98012.
I converted Issue Templates from
.md
to.yml
, please review my PR.Thanks!
Now the thing is i was waiting to work on it but all of a sudden you made a PR I was waiting as i was not assigned nor did i know if they even wanted these changes.
Anyways, good luck !