chore: add contribution governance docs and dotenv dependency

This commit is contained in:
Poyraz Avsever
2026-04-16 21:53:06 +03:00
parent d1b2d23509
commit b58951249e
10 changed files with 512 additions and 2 deletions
+52
View File
@@ -0,0 +1,52 @@
---
name: Bug report
about: Report a reproducible bug in OpenFrame
title: "bug: "
labels: [bug]
assignees: []
---
## Bug summary
What went wrong?
## Steps to reproduce
1.
2.
3.
## Expected behavior
What should have happened?
## Actual behavior
What happened instead?
## Environment
- OpenFrame version/branch:
- Bun version:
- Node version:
- Browser (if UI issue):
- OS:
## Relevant logs/errors
```text
Paste error logs, stack traces, or API errors here.
```
## Scope and impact
- [ ] Blocking
- [ ] High
- [ ] Medium
- [ ] Low
Who is affected and how?
## Additional context
Screenshots, recordings, or links.
+5
View File
@@ -0,0 +1,5 @@
blank_issues_enabled: true
contact_links:
- name: Questions and contribution help
url: https://github.com/yusufipk/OpenFrame/blob/main/CONTRIBUTING.md
about: Use issues for actionable tasks; for questions, include context and expected outcome.
+45
View File
@@ -0,0 +1,45 @@
---
name: Feature request
about: Suggest an improvement for OpenFrame
title: "feat: "
labels: [enhancement]
assignees: []
---
## Problem statement
What problem are you trying to solve?
## Proposed solution
What do you want to happen?
## Alternatives considered
What alternatives did you evaluate?
## Scope
Which areas are affected?
- [ ] API
- [ ] Auth/access
- [ ] Database
- [ ] UI/UX
- [ ] Docs
- [ ] DevEx/Operations
## Acceptance criteria
How will we know this is done?
- [ ] Criterion 1
- [ ] Criterion 2
## Non-goals (optional)
What is explicitly out of scope?
## Additional context
Mockups, examples, or references.
+62
View File
@@ -0,0 +1,62 @@
## Summary
Explain what changed in this PR.
## Why
Explain the problem this PR solves.
## Type of change
- [ ] feat
- [ ] fix
- [ ] docs
- [ ] refactor
- [ ] chore
- [ ] test
## Scope
What areas are affected?
- [ ] API routes
- [ ] Auth / access control
- [ ] Database schema / migration
- [ ] UI / UX
- [ ] Documentation
- [ ] Other
## Validation
- [ ] I ran `bun run check`.
- [ ] I ran `bun run db:generate` if `prisma/schema.prisma` changed.
- [ ] I manually tested affected flows.
Validation notes:
```text
Paste command output or manual test notes here.
```
## Breaking changes
- [ ] No breaking changes
- [ ] This PR introduces a breaking change (describe below)
If breaking, explain migration path:
## Database / migration notes
If schema changed, summarize migration impact.
## Screenshots / examples (if relevant)
Add screenshots or API request/response examples.
## Checklist
- [ ] PR title follows Conventional Commits (`type(scope): summary`).
- [ ] I used `successResponse` / `apiErrors` for API response changes.
- [ ] I used `auth()` and shared access checks (`checkProjectAccess` / `checkWorkspaceAccess`) where relevant.
- [ ] I updated docs when behavior changed.
- [ ] No secrets or unrelated file changes are included.