Git Contribution Guide & PR Standards
This guide outlines the unified Git contribution workflow required for the Elite Coders Summer of Code (ECSoC) 2026 cohort. Follow these steps to ensure clean history tracking, automatic check passes, and rapid PR approvals.
1. Forking & Cloning
Navigate to the target repository under the Elite Coders GitHub organization. Click the "Fork" button in the upper-right corner to create a copy of the repository under your personal GitHub account.
# Clone your fork locally
git clone https://github.com/YOUR_USERNAME/repo-name.git
# Add the official upstream repository as a remote
git remote add upstream https://github.com/elite-coders/repo-name.git
2. Branch Naming Conventions
Always create a new branch for each individual task or feature you work on. Do not make changes directly to the main or master branches.
# Create and switch to your feature branch
git checkout -b feat/your-feature-name
# Or for resolving issue bugfixes
git checkout -b fix/issue-number-description
3. Semantic Commit Messages
We enforce semantic committing to auto-generate changelogs and maintain readable commit sequences. Prefixes include:
- feat: A new user-facing feature update.
- fix: A bug fix resolved in code.
- perf: Code optimization targeting speed or render performance.
- docs: Documentation modifications or updates in Markdown files.
- refactor: Reorganizing structural logic without behavior alterations.
# Stage all files
git add .
# Create a semantic commit
git commit -m "feat: implement dynamic schema models for applications pipeline"
4. Push and Submitting Pull Request
Verify that tests compile locally before pushing. Submit the PR using the ECSoC template describing what was solved, linking related issues, and adding verify logs.
# Push changes to your origin remote
git push origin feat/your-feature-name