Open your first pull request
Apply an AI-native org's floor, its inherited baseline, and the request lifecycle in one hands-on contribution - a signed, Conventional-Commit, docs-complete pull request that passes the gates and stops for human review.
Units5
Duration21 min
Levelbeginner
By the end of this module, you'll be able to:
- Write a Conventional Commit - pick the right type and scope, and mark a breaking change correctly.
- Sign a commit so GitHub reports it Verified, and explain why signing is never disabled.
- Let the pre-commit hooks run (commitlint, secret scan, formatting) and explain why CI, not the hook, is the real gate.
- Satisfy docs-as-code and open a pull request that passes the gates and stops for human review.
Prerequisites
- Basic familiarity with Git and the command line.
- The earlier modules in this path, especially "Work the request lifecycle".
Units
- 01Introduction3 min
- 02Write a signed Conventional Commit6 min
- 03Pass the gates and open the PR6 min
- 04Knowledge check3 min
- 05Summary3 min
Related
- Inherit the project baseline How a new repository is born on the paved road with its whole ruleset already inherited, how to tell always-on standards from the ones a product type pulls in, and how to find an existing pattern before writing anything new.
- Work the request lifecycle Move a change through the seven-stage request lifecycle, understand why the write tools only propose, and read the Definition of Done that decides when a request is actually done rather than merely worked on.
- Apply a non-negotiable floor An AI-native org runs on a small floor every human and agent obeys. Study Cogitave's floor - its seven non-negotiable rules and what enforces each, from a commit-msg hook to policy-as-code - then apply a floor like it to your own first change.