Project Management

Gazprea is written by four people in one repository. This page describes how to run that on GitHub.

Best practices

Deliver every change through a pull request:

Branch from the default branch.
Commit your work to the branch and push it.
Open a pull request against the default branch.
A teammate who did not write it reviews and approves it.
Merge, and delete the branch.

Keep a pull request small enough that a teammate can read it in one sitting.

Track the work in issues:

Open an issue for each piece of work you have identified. Specification sections you have not implemented yet and test packages that are failing both divide cleanly into issues.
Assign every issue to the member doing it, and reassign it if the work changes hands.
Close issues as the work lands.

If your repository has no Issues tab, contact a TA. The tracker is disabled by default and only the teaching team can turn it on.

Marks

Project management is marked at Part 1 and again at Part 2. The lines and what each is worth are under Gazprea project management marks.

Enforcing them

You can enforce some of these rules with repository rulesets. Consider configuring them for your team’s repo.

Creating rulesets for a repository covers creating one under Settings → Rules → Rulesets, and Available rules for rulesets describes the rules you can choose from.

Creating or editing a ruleset requires repository admin. If you do not have admin permissions on your repo, contact a TA.

Warning

A ruleset applies to everyone it does not explicitly exempt, so it is possible to lock your own team out of your own default branch. Undoing that requires an organisation owner, so contact a TA rather than trying to recover it yourselves.

Note