Indirect Code Contribution 👻

Indirect Code Contribution

Looking at the commits and code that is part of a branch, we distinguish between 2 types of contribution to the branch.

Direct contribution - direct commits to the branch.

Indirect contribution - code that has a different origin branch and either merged to the current branch or cherrypicked into this branch.

LinearB is not counting indirect contributions as code changes. These changes are excluded from the work breakdown and commit count of the branch.

LinearB distinguishes between the 2 types of code. A direct contribution is counted into the individual's / team's active branches (WIP) count, commit count, cycle time, and work breakdown changes. Indirect code contribution on the other hand is already counted once on the smaller feature branch thus it is ignored when merged and is not counted for the second time.

Indirect work on a branch is marked with a ghost (👻) icon on a branch and when hovering opens a pop-up specifying the list of direct contributors as well as the number of indirect contributors.

How does indirect code affect an individuals active branches (WIP)?

when a developer contributes directly on 5 feature branches and an indirectly on 2 feature branches, the total number of active branches for this contributor will be 5.

How does indirect code affect an individual's work breakdown and code changes?

If a branch has 200 code changes that were committed directly and 500 more changes that were merged or cherrypicked from other branches, only the 200 direct changes will be counted for the work breakdown calculation.

How did we do?

Powered by HelpDocs (opens in a new tab)