Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Git at a hackathon: how to combine code and not lose your demo

На хакатоне Git помогает хранить общую историю проекта и соединять работу участников. Для небольшой команды достаточно простого порядка: основная ветка запускается, изменения делаются небольшими порциями, а перед объединением кто-то проверяет результат. Сложную модель ветвления лучше не вводить в середине соревнования. Git хранит версии файлов. GitHub и другие сервисы добавляют совместную работу,…

Translated from Russian Read in Russian

The article provides guidelines for using Git and GitHub during a hackathon. It advises teams to create a shared repository, set up access permissions, and choose a working branch. Team members should make small changes, test, and then merge their work after review, while also documenting changes and keeping track of versions. The article also recommends dividing work by files and interfaces, checking for conflicts, and verifying the project after merging changes.

Additionally, teams should save a version for protection, record a demo, and ensure that the project is reproducible and accessible to the judges.

Written by urgent.news from Dev.to's report — not a translation of it. Machine-written; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Investigating consumer lag without guesswork

Hi everyone, we’ve created a new project called Broka that supports Kafka, RabbitMQ, Redis, ActiveMQ Artemis, and Memcached. If you don't mind, I’d love to walk you through it with a quick guide.

  • Consumer lag in Kafka does not imply a consumer is caught up even when it's 0.
  • Stable consumer lag indicates a backlog, while a changing lag signifies task redistribution.

More from Wednesday 7 October →