{"author_link":"\/users\/lelek-hunor-kadosa","author_name":"L\u00e9lek Hunor Kadosa","author_uid":"lelek-hunor-kadosa","comments":[],"epoch":1728344767,"event":"LD56","format":"md","ldjam_node_id":404641,"likes":4,"metadata":{"p_key":"208387","p_author":"L\u00e9lek Hunor Kadosa","p_authorkey":"1244058","p_urlkey":"446745","p_title":"GitHub version control gives a completely different thrill","p_cat":"LDJam ","p_event":"LD56","p_time":"1728344767","p_likes":"4","p_comments":"0","p_status":"WAYBACK","us_key":"1244058","us_name":"L\u00e9lek Hunor Kadosa","us_username":"lelek-hunor-kadosa","event_start":"1728000000","event_key":"115","event_name":"Ludum Dare 56"},"node":{"_collation":{"body_sanitizer":"TextUtils::SanitizeHTML via existing importer","event":"LD56","removed_author":false},"_superparent":395186,"_trust":1,"author":244058,"body":"We know Unity has its own version control system, but since our team has 5 members and Unity VS is only free for teams of up to 3, we decided to use GitHub instead.\n\nIt works great as long as everyone sticks to completely separate scripts and scenes. But the moment two of us touch the same file, things fall apart. Chaos ensues\u2014there\u2019s confusion, frustration, and hours of lost work. We end up comparing branches after each push, trying to figure out who still has what.\n\nHave you experienced this kind of mess too? Are we doing something fundamentally wrong?","comments":1,"comments-timestamp":"2024-10-07T23:52:48Z","created":"2024-10-07T23:31:40Z","files":[],"files-timestamp":0,"id":404641,"love":4,"love-timestamp":"2024-10-08T12:35:49Z","meta":[],"modified":"2024-10-08T12:35:49Z","name":"GitHub version control gives a completely different thrill","node-timestamp":"2024-10-07T23:46:07Z","parent":400327,"parents":[1,5,9,395186,400327],"path":"\/events\/ludum-dare\/56\/swarmfall-protocol\/github-version-control-gives-a-completely-different-thrill","published":"2024-10-07T23:46:07Z","scope":"public","slug":"github-version-control-gives-a-completely-different-thrill","subsubtype":"","subtype":"","type":"post","version":1267989},"node_metadata":{"n_key":"404641","n_urlkey":"446745","n_parent":"400327","n_path":"\/events\/ludum-dare\/56\/swarmfall-protocol\/github-version-control-gives-a-completely-different-thrill","n_slug":"github-version-control-gives-a-c","n_type":"post","n_subtype":"","n_subsubtype":"","n_author":"244058","n_created":"1728343900","n_modified":"1728390949","n_version":"1267989","n_status":"WAYBACK"},"source_url":"https:\/\/ldjam.com\/events\/ludum-dare\/56\/swarmfall-protocol\/github-version-control-gives-a-completely-different-thrill","text":"We know Unity has its own version control system, but since our team has 5 members and Unity VS is only free for teams of up to 3, we decided to use GitHub instead.\n\nIt works great as long as everyone sticks to completely separate scripts and scenes. But the moment two of us touch the same file, things fall apart. Chaos ensues\u2014there\u2019s confusion, frustration, and hours of lost work. We end up comparing branches after each push, trying to figure out who still has what.\n\nHave you experienced this kind of mess too? Are we doing something fundamentally wrong?","title":"GitHub version control gives a completely different thrill","wayback_source":[]}