Developer Enablement & Knowledge

Developer Resources

“Learn to make first PR”

Step-by-step guidance, git fundamentals, interactive pull request checklists, and in-depth technical blogs. Switch between resources using the top navbar options.

Foundational Knowledge

Learn Pull Requests (Learn to PR)

Git Architecture

Understanding the Pull Request Lifecycle

A pull request (PR) is a formal proposal to merge changes from your independent branch or fork into an upstream codebase. It provides a collaborative forum for peer code reviews, automated CI checks, and architectural validation before code hits production.

Origin vs. Upstream: Maintain a synchronized link with the main campus repository

Feature Branches: Always isolate your work onto dedicated branch names

Atomic Commits: Keep each commit focused on one cohesive logical change

Engineering Etiquette

Conventional Commit Standards

ZenithenOpen projects enforce the Conventional Commits specification to generate automated release changelogs and maintain clean git histories.

feat: Introduces a new user-facing feature (e.g., feat: add dark theme switcher)

fix: Patches an existing software defect (e.g., fix: resolve sidebar overflow on mobile)

docs: Updates documentation, markdown files, or guides

refactor: Restructures existing code without altering external behavior

Advanced Workflow

Resolving Git Merge Conflicts

Merge conflicts happen when two branches modify the same lines of code. Resolving them cleanly is a critical skill for any professional open-source software engineer.

Pull latest changes from upstream main before opening or updating a PR

Use git rebase upstream/main to replay your commits cleanly on top

Resolve conflicts in your IDE, verify builds, and push with confidence