chore: add CONTRIBUTING, PR template, and CODEOWNERS to require PRs

[Copilot]

Establishes PR-first workflow foundation by adding three governance files. No CI enforcement yet—documentation only.

Files Added

• .github/CODEOWNERS — Assigns @Vamsi-o as code owner for all files
• .github/PULL_REQUEST_TEMPLATE.md — Standard template with summary, changes, testing, and checklist sections
• CONTRIBUTING.md — Documents branch naming conventions, PR requirements, review process, and issue guidelines

All future changes should follow the branch → PR → review → merge workflow documented in CONTRIBUTING.md.

Original prompt

Create a new branch named copilot/protect-main and add three files to the repository to enforce a PR-first workflow (no CI yet). Files to add (exact contents):

1. .github/CODEOWNERS

* @Vamsi-o

2. .github/PULL_REQUEST_TEMPLATE.md

## Summary

<!-- Short description of the change. -->

## What changed
- Describe what you changed and why.

## How to test
- Steps to reproduce / test this PR locally.

## Checklist
- [ ] I opened this PR from a feature branch (not main)
- [ ] CI builds and tests pass (no CI configured yet)
- [ ] I added/updated tests if applicable
- [ ] I added documentation if applicable

## Reviewers
- @Vamsi-o (code owner) will be automatically requested to review.

3. CONTRIBUTING.md

# Contributing to BuildFlow

Thank you for contributing! To keep the project stable and reviewable, follow these rules:

1. Branches and commits
   - Always create a branch for your work; do not commit directly to `main`.
   - Use descriptive branch names like `feature/add-x` or `fix/issue-123`.

2. Pull Requests
   - Open a Pull Request from your branch into `main`.
   - Use the PR template (.github/PULL_REQUEST_TEMPLATE.md). Describe the change and how to test it.
   - A Code Owner review is required (see .github/CODEOWNERS) — @Vamsi-o is requested by default.
   - The `ci` status check is not required yet; CI will be added later.

3. Reviews and merging
   - A code owner (or an assigned reviewer) should approve the PR before merging.
   - Once approved, a maintainer can merge the PR into `main`.

4. Issues
   - Open an issue before implementing non-trivial changes to discuss design and scope.

If you'd like stricter automation (e.g., required status checks, automatic merges after approval), we can add CI and automation in a follow-up PR.

Please create the branch copilot/protect-main, add these files with an initial commit, and open a pull request from copilot/protect-main into main with the title "chore: add CONTRIBUTING, PR template, and CODEOWNERS to require PRs". Do not merge the PR. No CI workflow or additional changes beyond these three files.

This pull request was created as a result of the following prompt from Copilot chat.

Create a new branch named copilot/protect-main and add three files to the repository to enforce a PR-first workflow (no CI yet). Files to add (exact contents):

1. .github/CODEOWNERS

* @Vamsi-o

2. .github/PULL_REQUEST_TEMPLATE.md

## Summary

<!-- Short description of the change. -->

## What changed
- Describe what you changed and why.

## How to test
- Steps to reproduce / test this PR locally.

## Checklist
- [ ] I opened this PR from a feature branch (not main)
- [ ] CI builds and tests pass (no CI configured yet)
- [ ] I added/updated tests if applicable
- [ ] I added documentation if applicable

## Reviewers
- @Vamsi-o (code owner) will be automatically requested to review.

3. CONTRIBUTING.md

# Contributing to BuildFlow

Thank you for contributing! To keep the project stable and reviewable, follow these rules:

1. Branches and commits
   - Always create a branch for your work; do not commit directly to `main`.
   - Use descriptive branch names like `feature/add-x` or `fix/issue-123`.

2. Pull Requests
   - Open a Pull Request from your branch into `main`.
   - Use the PR template (.github/PULL_REQUEST_TEMPLATE.md). Describe the change and how to test it.
   - A Code Owner review is required (see .github/CODEOWNERS) — @Vamsi-o is requested by default.
   - The `ci` status check is not required yet; CI will be added later.

3. Reviews and merging
   - A code owner (or an assigned reviewer) should approve the PR before merging.
   - Once approved, a maintainer can merge the PR into `main`.

4. Issues
   - Open an issue before implementing non-trivial changes to discuss design and scope.

If you'd like stricter automation (e.g., required status checks, automatic merges after approval), we can add CI and automation in a follow-up PR.

Please create the branch copilot/protect-main, add these files with an initial commit, and open a pull request from copilot/protect-main into main with the title "chore: add CONTRIBUTING, PR template, and CODEOWNERS to require PRs". Do not merge the PR. No CI workflow or additional changes beyond these three files.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Vamsi-o]

@copilot so how does this work ,

[Copilot]

@copilot so how does this work ,

These three files establish the foundation for a PR-first workflow:

1. CODEOWNERS - Automatically requests you as a reviewer on every PR, ensuring code review happens
2. PULL_REQUEST_TEMPLATE.md - Provides a standard checklist when opening PRs (includes reminder to use feature branches)
3. CONTRIBUTING.md - Documents the workflow rules for all contributors

How it enforces PRs:

• CODEOWNERS ensures you're notified of all changes
• The template guides contributors to follow best practices
• Documentation sets clear expectations

Next steps for stricter enforcement:

• Enable branch protection on main (requires PR reviews before merge)
• Add CI checks as status requirements
• Consider adding a GitHub Action to auto-assign reviewers

Right now, this is documentation-based enforcement. For technical enforcement, you'll need to configure branch protection rules in GitHub Settings → Branches.