You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: formalize strict issue-first fork-and-PR contribution workflow in CONTRIBUTING.md #1
Update CONTRIBUTING.md to establish and formalize the mandatory 5-step contribution protocol for all contributors and automated agents.
Context & Workflow Rules
To maintain clean code governance and traceability across the project:
GitHub Issue First: All work must start with an issue opened in the upstream repository (geekinks/problemspot). Direct changes without an issue are not accepted.
Fork & Dedicated Branch: Contributors must fork geekinks/problemspot to their personal GitHub account, sync with upstream/main, and create a dedicated feature branch (<type>/<kebab-case-description>). Commits directly to main are prohibited.
Implement, Verify & Commit: Adhere to code standards, TypeScript strict typing, brand guidelines (brand.md), and run test suites and linters locally. Commit using Conventional Commits.
Push & Open PR: Push the branch to the personal fork (origin) and open a PR targeting geekinks/problemspot:main referencing the issue (Closes #...).
Review & Squash Merge: Maintainers review the PR. Once approved and CI checks pass, maintainers squash-merge into main and delete the branch. Contributors sync their local main back from upstream/main.
Acceptance Criteria
Update CONTRIBUTING.md with the explicit 5-step contribution lifecycle.
Add explicit instructions that all issues must be opened in the main repo (geekinks/problemspot).
Activity
Merge pull request #1 from geekinks/main
Merge pull request #11 from Icedmist/main