BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2024//talk//SAWP3R
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-europython-2024-SAWP3R-0@programme.europython.eu
DTSTART;TZID=CET:20240708T134500
DTEND;TZID=CET:20240708T151500
DESCRIPTION:Maintaining code quality can be challenging\, no matter the siz
 e of your project or number of contributors. Different team members may ha
 ve different opinions on code styling and preferences for code structure\,
  while solo contributors might find themselves spending a considerable amo
 unt of time making sure the code conforms to accepted conventions. However
 \, manually inspecting and fixing issues in files is both tedious and erro
 r-prone. As such\, computers are much more suited to this task than humans
 . Pre-commit hooks are a great way to have a computer handle this for you.
 \n\nPre-commit hooks are code checks that run whenever you attempt to comm
 it your changes with Git. They can detect and\, in some cases\, automatica
 lly correct code-quality issues *before* they make it to your code base. I
 n this tutorial\, you will learn how to install and configure pre-commit h
 ooks for your repository to ensure that only code that passes your checks 
 makes it into your code base. We will also explore how to build custom pre
 -commit hooks for novel use cases.\n\n## Prerequisites\n- Comfort writing 
 Python code and working with Git on the command line using basic commands 
 (e.g.\, clone\, status\, diff\, add\, commit\, and push)\n- Have Python an
 d Git installed on your computers\, as well as a text editor for writing c
 ode (e.g.\, Visual Studio Code)\n\n## Prepare for the workshop\n1. Fork an
 d clone [this repository](https://github.com/stefmolin/pre-commit-workshop
 ).\n2. Create a virtual environment for this workshop using whichever tool
  you prefer.\n3. Run `pip install pre-commit` (or equivalent) in your acti
 vated virtual environment.\n4. Brainstorm some ideas for your hook.\n\n## 
 Feedback?\nLet me know what you thought by filling out [this feedback form
 ](https://stefaniemolin.com/feedback/).
DTSTAMP:20260310T184532Z
LOCATION:Club E
SUMMARY:(Pre-)Commit to Better Code - Stefanie Molin
URL:https://programme.europython.eu/europython-2024/talk/SAWP3R/
END:VEVENT
BEGIN:VEVENT
UID:pretalx-europython-2024-SAWP3R-1@programme.europython.eu
DTSTART;TZID=CET:20240708T153000
DTEND;TZID=CET:20240708T170000
DESCRIPTION:Maintaining code quality can be challenging\, no matter the siz
 e of your project or number of contributors. Different team members may ha
 ve different opinions on code styling and preferences for code structure\,
  while solo contributors might find themselves spending a considerable amo
 unt of time making sure the code conforms to accepted conventions. However
 \, manually inspecting and fixing issues in files is both tedious and erro
 r-prone. As such\, computers are much more suited to this task than humans
 . Pre-commit hooks are a great way to have a computer handle this for you.
 \n\nPre-commit hooks are code checks that run whenever you attempt to comm
 it your changes with Git. They can detect and\, in some cases\, automatica
 lly correct code-quality issues *before* they make it to your code base. I
 n this tutorial\, you will learn how to install and configure pre-commit h
 ooks for your repository to ensure that only code that passes your checks 
 makes it into your code base. We will also explore how to build custom pre
 -commit hooks for novel use cases.\n\n## Prerequisites\n- Comfort writing 
 Python code and working with Git on the command line using basic commands 
 (e.g.\, clone\, status\, diff\, add\, commit\, and push)\n- Have Python an
 d Git installed on your computers\, as well as a text editor for writing c
 ode (e.g.\, Visual Studio Code)\n\n## Prepare for the workshop\n1. Fork an
 d clone [this repository](https://github.com/stefmolin/pre-commit-workshop
 ).\n2. Create a virtual environment for this workshop using whichever tool
  you prefer.\n3. Run `pip install pre-commit` (or equivalent) in your acti
 vated virtual environment.\n4. Brainstorm some ideas for your hook.\n\n## 
 Feedback?\nLet me know what you thought by filling out [this feedback form
 ](https://stefaniemolin.com/feedback/).
DTSTAMP:20260310T184532Z
LOCATION:Club E
SUMMARY:(Pre-)Commit to Better Code - Stefanie Molin
URL:https://programme.europython.eu/europython-2024/talk/SAWP3R/
END:VEVENT
END:VCALENDAR