yusufipek/OpenFrame
1
0
Fork 0
mirror of https://github.com/yusufipk/OpenFrame.git synced 2026-09-11 17:46:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: update branch references from 'main' to 'master' in configuration and documentation files

Browse Source
This commit is contained in:
poyrazavsever
2026-04-18 17:15:59 +03:00
parent ce2b3e5976
commit ac70f657cb
4 changed files with 3 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/ISSUE_TEMPLATE/config.yml
+1 -1
View File
@@ -1,5 +1,5 @@
blank_issues_enabled: true blank_issues_enabled: true
contact_links: contact_links:
- name: Questions and contribution help - name: Questions and contribution help
url: https://github.com/yusufipk/OpenFrame/blob/main/CONTRIBUTING.md url: https://github.com/yusufipk/OpenFrame/blob/master/CONTRIBUTING.md
about: Use issues for actionable tasks; for questions, include context and expected outcome. about: Use issues for actionable tasks; for questions, include context and expected outcome.
CODEOWNERS
-8
View File
@@ -1,10 +1,2 @@
# Global default owners # Global default owners
* @yusufipk * @yusufipk
# Critical security and access control areas
/lib/auth.ts @yusufipk
/lib/route-access.ts @yusufipk
/app/api/auth/ @yusufipk
/app/api/stripe/ @yusufipk
/prisma/ @yusufipk
CONTRIBUTING.md
+1 -38
View File
@@ -62,7 +62,7 @@ bun run db:seed
## Contribution Workflow ## Contribution Workflow
1. Fork and create a branch from `main`. 1. Fork and create a branch from `master`.
2. Keep changes focused on one logical concern. 2. Keep changes focused on one logical concern.
3. Follow coding and architecture conventions in this guide. 3. Follow coding and architecture conventions in this guide.
4. Run required validation locally. 4. Run required validation locally.
@@ -179,43 +179,6 @@ When changing data model behavior:
- For technical changes, document behavior in the most relevant existing file or PR notes. - For technical changes, document behavior in the most relevant existing file or PR notes.
- Keep docs practical and update them in the same PR when behavior changes. - Keep docs practical and update them in the same PR when behavior changes.
## Pull Request Checklist
Before submitting, confirm:
- [ ] My branch is focused on one concern.
- [ ] I followed project conventions in this guide.
- [ ] I ran `bun run check`.
- [ ] I ran `bun run db:generate` if schema changed.
- [ ] I updated docs for user-visible or architectural changes.
- [ ] I added screenshots or request/response examples when useful.
- [ ] My PR description explains what changed and why.
## PR Description Template (Recommended)
```markdown
## Summary
Short description of what changed.
## Why
What problem this solves.
## Changes
- Key change 1
- Key change 2
## Validation
- bun run check
- Manual test notes
## Notes
Any migration, compatibility, or follow-up notes.
```
## Review Expectations ## Review Expectations
SECURITY.md
+1 -1
View File
@@ -3,7 +3,7 @@
## Supported Versions ## Supported Versions
OpenFrame is under active development. OpenFrame is under active development.
Security fixes are prioritized for the latest code on `main` and recent release tags (if available). Security fixes are prioritized for the latest code on `master` and recent release tags (if available).
## Reporting a Vulnerability ## Reporting a Vulnerability