Skip to content

chore: CODEOWNERS + release policy #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mdtazizulislam wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: CODEOWNERS + release policy #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Default owners for entire repo
* @mdislam7895121

# Optional: workflow ownership (keep you as owner)
.github/workflows/* @mdislam7895121
26 changes: 26 additions & 0 deletions docs/RELEASE_POLICY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Release Policy

This repo uses a protected main branch. All changes must go through PRs and pass required checks.

## Versioning
- Use semantic version tags: vMAJOR.MINOR.PATCH
- Examples: v1.0.0, v1.2.3

## When to tag a release
- Tag only after a PR is merged into main and all required checks pass.
- Tag should point to a merge commit on main.

## How to create a release tag (PowerShell)
1) Sync main:
git checkout main
git pull --ff-only

2) Create an annotated tag:
git tag -a vX.Y.Z -m "release: vX.Y.Z"

3) Push the tag:
git push origin vX.Y.Z

## Notes
- Never force-push tags.
- If a release is bad, create a new patch release tag.