<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tips on Alexander Junge&#39;s website</title>
    <link>https://www.alexanderjunge.net/categories/tips/</link>
    <description>Recent content in Tips on Alexander Junge&#39;s website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 12 Nov 2022 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.alexanderjunge.net/categories/tips/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Keeping sensitive information out of Jupyter notebooks stored in git version control</title>
      <link>https://www.alexanderjunge.net/blog/sensitive-info-out-of-jupyter-notebooks/</link>
      <pubDate>Sat, 12 Nov 2022 00:00:00 +0000</pubDate>
      
      <guid>https://www.alexanderjunge.net/blog/sensitive-info-out-of-jupyter-notebooks/</guid>
      <description>Jupyter notebooks are very useful to quickly prototype ideas in data science projects because they allow seeing code, the output of that code, and a narrative explaining its logic right next to each other. But when committing said Jupyter notebooks to version control systems like git, code output containing sensitive information (such as passwords, access tokens, or sensitive data) can easily end up being stored in places where it should not be stored and where it is accessible to others.</description>
    </item>
    
    <item>
      <title>Sanity checking your git commits</title>
      <link>https://www.alexanderjunge.net/blog/git-pre-commit-checks/</link>
      <pubDate>Tue, 21 Jan 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.alexanderjunge.net/blog/git-pre-commit-checks/</guid>
      <description>Most projects I am working on enforce specific code styles, minimal requirements for documentation, or other rules every code contribution needs to follow. Git pre-commit hooks are very useful to automatically check that commits fulfill these requirements. This allows all project contributors to focus on the code instead of manually running different code formatters or wasting time in unnecessary arguments over missing whitespace.
Installing the pre-commit package manager Pre-commit hooks are managed via the pre-commit package manager which can be installed from PyPI:</description>
    </item>
    
  </channel>
</rss>