@@ -58,6 +58,37 @@ We have one seminar group open.
TBA
### Project
Your group has been tasked with writing a blog post about... the Git course you are currently taking! (Wow, ground-breaking, we know.)
The goal is to move beyond individual commands and work together as a real-world development team.
***Platform** - A GitLab repository (we’ve set this up for you!)
***Format** - Strictly Markdown (.md)
***Language** - English or CzechoSlovak (just pick one be consistent)
***Length** - Total words ≥100×number of students
***Quality Control** - A CI/CD Pipeline is deployed. Your code must pass the lint rules.
#### What is expected from you as individual
Even though you are a part of a team the participation of every member is expected.
These are some requirements on you as an individual:
***Contribute**: Everyone must write at least one section of the blog.
***The MR Lifecycle**: Every member must create, manage, and merge their own Merge Request (MR).
***Peer Review**: You are required to review and approve at least **two** MRs from your teammates.
**Important**: As an approver, you share responsibility for the content! If the pipeline breaks or there’s a typo, it’s on the author and the reviewers. Check those lint rules before hitting "Approve."
Some ideas that might help you:
* Communicate with your team!
* Create issues specifying what will each of you cover and who will be your approver.
* Elect a person that will work as a leader and will be in charge leading the discussions.
