chore: repo alignment (#9256)

align repo to Hypermode:
- issue templates
- PR templates
- code of conduct
- Renovate for dependency management
- copyright and other legal references

Author: ryanfoxtyler

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ""
+labels: bug
+assignees: ""
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+## To Reproduce
+
+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.
+
+## Environment
+
+- OS: [e.g. macOS, Windows, Ubuntu]
+- Language [e.g. AssemblyScript, Go]
+- Version [e.g. v0.xx]
+
+## Additional context
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Dgraph Community Support
+    url: https://discord.hypermode.com
+    about: Please ask and answer questions here

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ""
+labels: ""
+assignees: ""
+---
+
+## 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 [...]
+
+## Describe the solution you'd like
+
+A clear and concise description of what you want to happen.
+
+## Describe alternatives you've considered
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+## Additional context
+
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,13 +1,26 @@
-# Title format
+**Description**
 
-- `Topic(Area): Feature`
-- `Topic` must be one of `build|ci|docs|feat|fix|perf|refactor|chore|test`
-- `Area` must be one of `acl|audit|backup|badger|cdc|dql|export|graphql|indexing|multi-tenancy|raft|restore|upgrade|zero`
-- Add [BREAKING] if it is a breaking change
+Please explain the changes you made here.
 
-# Body Format
+**Checklist**
 
-Description: {add description}
-Fixes: {GitHub Issue}
-Closes: {Linear Issue}
-Docs: {docs PR}
+- [ ] Code compiles correctly and linting passes locally
+- [ ] For all _code_ changes, an entry added to the `CHANGELOG.md` file describing and linking to
+      this PR
+- [ ] Tests added for new functionality, or regression tests for bug fixes added as applicable
+- [ ] For public APIs, new features, etc., PR on [docs repo](https://github.com/dgraph-io/dgraph-docs)
+      staged and linked here
+
+**Instructions**
+
+- The PR title should follow the [Conventional Commits](https://www.conventionalcommits.org/)
+  syntax, leading with `fix:`, `feat:`, `chore:`, `ci:`, etc.
+- The description should briefly explain what the PR is about. In the case of a bugfix, describe or
+  link to the bug.
+- In the checklist section, check the boxes in that are applicable, using `[x]` syntax.
+  - If not applicable, remove the entire line. Only leave the box unchecked if you intend to come
+    back and check the box later.
+- Delete the `Instructions` line and everything below it, to indicate you have read and are
+  following these instructions. 🙂
+
+Thank you for your contribution to Dgraph!

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,4 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": ["github>hypermodeinc/renovate-config"]
+}