T Tool or technology HF-D7.4-003 sector-specific 10 skills
Version control and collaboration workflow
Works with a version control system, uses branches and merge requests and keeps the change history traceable for the team.
How hrmforce measures this
- Assessment method
- Work sample test · rho 0.33 (SD 0.09)
- hrmforce instrument
- Work sample test
- Competency (50-framework)
- Collaborate
- Trainability
- high
- Demand outlook 2026 to 2030
- stable
The candidate performs a representative work sample under standardised conditions.
Behavioural anchors
| Level | Behaviour at this level |
|---|---|
| N1 Guided | Commits changes with a clear description in the designated branch according to the team agreement. works under supervision and follows instruction · routine, one variable at a time · own task |
| N3 Proficient | Manages branches and merges independently, resolves conflicts and reviews colleagues' changes on substance. sets own approach and seeks input proactively · several variables, some ambiguity · own team or process |
| N5 Leading | Determines the way of working for version control and code review in the organisation and enforces it across teams. sets the standard and the policy · strategic, under high uncertainty · organisation, value chain or profession |
N2 and N4 are deliberately not anchored. Raters place them between the anchors, following the O*NET convention.
Underlying skills
These skills inherit the assessment route and the behavioural anchors of this construct.
| T | Skill | Definition | Demand outlook 2026 to 2030 |
|---|---|---|---|
| T | Using Git Git | Manages changes with Git through commits, branches, merging and reverting earlier versions. | stable |
| T | GitHub GitHub | Collaborates on GitHub with repositories, issues, pull requests and automated checks. | rising |
| T | GitLab GitLab | Works in GitLab with projects, merge requests, pipelines and permission management per group. | stable |
| T | Azure DevOps Azure DevOps | Manages work items, repositories and pipelines in Azure DevOps and links code to planning and delivery. | stable |
| V | Applying a branching strategy Branching strategy | Follows an agreed way of working for branches and releases so work runs in parallel without breaking the main line. | stable |
| V | Reviewing a pull request Pull request review · Code review | Reviews proposed changes for behaviour, readability and risk and gives concrete, verifiable comments. | rising |
| G | Giving a code review Code review feedback | Discusses code with the author, separates blocking issues from suggestions and keeps the tone focused on content. | rising |
| V | Resolving a merge conflict Merge conflict | Resolves conflicting changes by understanding both intentions and retesting the result. | stable |
| V | Setting up a CI pipeline CI pipeline · Continuous integration | Sets up a pipeline that builds on every change, runs tests and reports the result back to the team. | rising |
| V | Applying semantic versioning Semantic versioning | Assigns version numbers that indicate whether a change affects existing users and maintains a changelog. | stable |