Swimlanes 31e4f37556277c9523f9d989414ea80df21e470444f4166953b3f15599c449fa+41e2e862abce78d1a655c6012586b2535e1f9088bdadb201b2e68d594499c069+74bbbc259910ab5229939c3ec81afe848a221d4bade315325716b96e1dc56d4f+75ceba7479600e5cf590b136c67b90c2299cf47ed5b86ebb6fc0a2ff8daf55a1+f1159d783f9c62c50e4e1c1f8346cf1963c24d46f71eb901330da821da4c01a5 · 32 changes in 13 lanes
Changes that do not depend on each other run in separate lanes, oldest on the left; an edge joins a change to what it depends on. There are no merge nodes: parallel work simply stays parallel. list view