A recent contribution can show how project structure, access, and review work together. These questions help you examine that experience with the people involved. Differences between the instructions and what happened may explain why a change waited or needed help.
You don't need to answer every question at once. A project move, a new supported template, or a delayed contribution will each call for a different part of the checklist. When you agree on an improvement, give someone responsibility for it and return to the affected work to see whether it helped.
Project purpose and responsibility
Project structure that supports how teams deliver helps you weigh keeping work together against the independence separate projects can provide.
- Can a contributor explain what the project delivers and who is responsible for review, release, support, and eventual retirement?
- Does the structure let related changes move together, without repeatedly coordinating the same owners across several projects?
- Do separate projects provide independence in access, legal requirements, releases, or operation that the teams actually use?
- Can someone find the required dependency versions, release order, and responsible teams for a change that spans projects?
- Before splitting a slow monorepo, has the team considered clone and fetch demand, history, references, large files, concurrent pipelines, and unnecessary jobs?
Review that covers the final change
Protected changes with independent review explains how to choose reviewers and arrange permissions so the final change receives their attention.
- Do important branches require the intended merge request path, including for service accounts and deploy keys?
- Have exact, wildcard, group, and project rules been considered together, including who can change or remove protection?
- Does someone other than the author or committers assess the current diff before it merges?
- Where approvals are a team agreement rather than an enforced requirement, does the person merging check that the review happened?1
- Can eligible reviewers satisfy every required rule during ordinary work and absences, without an unsatisfiable ordinary rule being auto-approved?
- Do approvals still cover the final change, including after a new commit or the team's usual rebase operation?
- Can a later reader follow the reason, checks, approval, and any exception or unresolved follow-up from the merge request?
- When review takes longer than expected, can the team distinguish missing context or an unavailable reviewer from time spent investigating the change?
A working start and a maintainable setup
Project setup teams can use and maintain describes how to support the first contribution and later updates.
- Can a team create a project, run its first pipeline, and complete a reviewed change with ordinary contributor access and the published instructions?
- Can contributors understand any intentional permission request and find the person who handles it?
- Does the team know which files were copied, which components are versioned, and which settings or policies continue to apply?
- Do the supported choices fit the work, rather than requiring teams to remove or repair the same parts each time?
- Can existing projects adopt improvements to copied files and components without starting over?
- Do shared branch rules still have the intended effect alongside each project's matching rules?
- Can someone resolve a legitimate exception and arrange to revisit it?
Finding work and contributing across teams
Contributions that work across teams follows a contribution from finding the project through review and adoption.
- Can someone outside the team find the project and understand its purpose, supported use, maintenance status, and owners?
- Can that person prepare a change, run the relevant checks, and request review without private instructions?
- Do templates ask for information reviewers act on, and can contributors find supported components instead of copying their implementation?
- Are decisions made in meetings or chat explained with the work they affect?
- Can contributors propose changes with appropriate access, without exposing confidential work or obtaining unnecessary write permissions?
- Do maintainers review submitted code and CI changes before running a fork's pipeline with parent-project resources?
- Does someone respond to review requests, cover absences, and explain how an accepted change will reach its consumers?
When projects move or ownership changes
A move deserves attention beyond the Git repository. The project structure recommendation explains how to plan around the work that depends on its current location.
- Will the intended contributors retain access, and are any permissions inherited from the destination appropriate?
- Does the transfer or migration plan account for collaboration history, pipelines, registries, integrations, credentials, and dependencies?
- Are path changes, registry restrictions, and changes to policy or compliance framework coverage understood before the move?
- Can people complete a contribution, pipeline, and release afterward, including any cross-project dependencies?
- Have owners updated the instructions and resolved gaps before repeating the move more widely?
Further Reading
Notes
-
Required approvals and approval settings are available in Premium and Ultimate. Free supports optional approvals, which don't block a merge. ↩
- Related work and ownership in one project explains the reasoning behind project splits and moves.
- Independent reviews and change history explains what makes a review independent and current.
- Safe self-service with supported defaults considers the responsibilities behind a supported project setup.
- Easy-to-find work and consistent contribution steps explains how project information and recorded decisions reduce repeated handoffs.