New game
Download
Get Academic Plan
Share game
Fill in the Blanks
Fill in the Blanks

Gitflow vs Trunk-Based

Integrate it into your platform

You can integrate the game into an LMS compatible with LTI 1.1 or LTI 1.3 such as Canvas, Moodle, or Blackboard. This way, the scores will be automatically saved into the platform’s gradebook.
Download
You have exceeded the maximum number of games you can integrate into Google Classroom with your current Plan.

To integrate as many games as you want in Google Classroom, you need an Academic Plan or a Commercial Plan.

You have exceeded the maximum number of games you can integrate into Microsoft Teams with your current Plan.

To integrate as many games as you want in Microsoft Teams, you need an Academic Plan or a Commercial Plan.

Downloading games is an exclusive feature for users with an Academic Plan or a Commercial Plan.

Get your Academic Plan or your Commercial Plan now and start integrating your games into your LMS, website or blog.

If you wish, you can download a demo game here and test its integration:

Gitflow vs Trunk-Based

Fill in the Blanks

Played 3 %Accuracy 100 Average time 01:35

About this activity

Gitflow vs Trunk-Based

Created by

Spain

Download the paper version to play

Make your own free game from our game creator
Compete against your friends to see who gets the best score in this game

Top Games

%
Anonymous
Anonymous
%
%
%
You have exceeded the maximum number of games you can print with your current Plan.

To print as many games as you want, you need an Academic Plan or a Commercial Plan.

Print your game
Gitflow vs Trunk-Based
 

Fill in the Blanks

Gitflow vs Trunk-BasedOnline version

Gitflow vs Trunk-Based

by César Criado Núñez
1

El desarrollo orientado a motiva a los equipos a fusionar sus cambios en la rama al menos una vez al día . Este método elimina el aislamiento de las ramas de larga duración , evitando así el famoso de las fusiones al final de un proyecto . Al integrar código con frecuencia , el equipo recibe inmediato sobre la estabilidad del sistema mediante procesos automáticos . La reducción del tamaño de los cambios a lotes permite identificar errores rápidamente y facilita una revisión más exhaustiva . Gracias a esta disciplina , el código permanece en un estado constantemente , agilizando el tiempo de llegada al mercado . Por el contrario , las ramas de funcionalidades extensas dificultan la técnica y aumentan el riesgo de divergencia en el código . "

Are you sure you want to leave the page?

If you leave, you will lose the game in progress.