Hub Conectadas in Brasília announced a workshop on Python, Git and GitHub for November 28, 2026. The day’s program runs from 8:30 a.m. to 6 p.m. on the fourth floor of Mané Garrincha Stadium. The activities are free for women interested in technology, with advance registration. The stated hours cover the day, which also includes other activities. Check eligibility and available places in the announcement. Your club’s paper version needs no computer. Program from Agência Brasília

Prepare two files and save their first version

Advertisementpreview

Label one card Route and write “start at gate A.” Label another Supplies and write “chalk.” These two cards on the table are the files you will edit. Make a copy of each and put them in envelope 1. Write “First version of the activity” on the front.

Each envelope stands for a commit, a record of what the project files looked like at one point in the project’s history. The message on the front says what the version records. Git keeps a reference to the files in each version. When a file’s contents stay the same, Git can reuse the content it already has. The paper exercise uses a full copy of each card to show everything that belongs in each version. Official Pro Git book on snapshots

Read alsoBrazil’s HPE25 championship in Bahia: find where the wind comes from

Make two changes in separate versions

• On the Route card, change the starting point to gate B. Copy both current cards into envelope 2. Write “Change the starting gate.” The Supplies card still lists chalk.
• On the Supplies card, add cones. Copy the two current cards into envelope 3. Write “Add cones to mark the course.” The Route card still starts at gate B.
• Ask someone to read the messages and predict which card changed in each round. They can open the envelopes side by side to check.

Advertisementpreview

GitHub’s documentation on comparing commits explains how to view the changes between two points in a project’s history. Your unit compares cards on a table. Open envelope 2 and you can see everything that applied at that point, including the supplies that remained the same. GitHub documentation on comparing commits

Bring back just one piece of an older version

Imagine gate B is now closed. Open envelope 1 and copy only its Route card onto the table. Keep the chalk and cones from envelope 3 on the Supplies card. Then make envelope 4 with a copy of both current cards. Write “Return to gate A and keep the cones.”

Give the latest version to someone who joined the exercise late. Ask them to compare the message to the two cards inside. They should find gate A on one card and chalk plus cones on the other. Envelope 3 is still there to show what the plan looked like before the change. If two envelopes have been mixed up, go through that step again and make a fresh copy of each card before filing it.