<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PR on Dev notes</title>
    <link>https://blog.michal.pawlik.dev/tags/pr/</link>
    <description>Recent content in PR on Dev notes</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 May 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.michal.pawlik.dev/tags/pr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Useful commands for inspecting sbt build</title>
      <link>https://blog.michal.pawlik.dev/posts/til/inspecting-sbt/</link>
      <pubDate>Wed, 29 May 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.michal.pawlik.dev/posts/til/inspecting-sbt/</guid>
      <description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Today I learned a few useful commands to help you understand complex sbt builds.&lt;/p&gt;&#xA;&lt;h2 id=&#34;task-timing&#34;&gt;task timing&lt;/h2&gt;&#xA;&lt;p&gt;JAVA_OPTS=-Dsbt.task.timings=true sbt&lt;/p&gt;&#xA;&lt;h2 id=&#34;inspecting-task&#34;&gt;inspecting task&lt;/h2&gt;&#xA;&lt;p&gt;inspect module/taskName&lt;/p&gt;&#xA;&lt;h2 id=&#34;inspecting-task-tree&#34;&gt;inspecting task tree&lt;/h2&gt;&#xA;&lt;p&gt;inspect tree module/taskName&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hide irrelevant data in your PRs</title>
      <link>https://blog.michal.pawlik.dev/posts/til/cleaner-pr-diffs/</link>
      <pubDate>Fri, 05 Jan 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.michal.pawlik.dev/posts/til/cleaner-pr-diffs/</guid>
      <description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Today I learned that you can &lt;a href=&#34;https://docs.github.com/en/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github&#34;&gt;hide irrelevant changes from Github PRs&lt;/a&gt;. The syntax for &lt;code&gt;.gitattributes&lt;/code&gt; can be tricky though.&lt;/p&gt;&#xA;&lt;p&gt;In my current project, it&amp;rsquo;s sometimes necessary to re-generate and commit a bunch of files to the repository. This can happen when you store some &lt;a href=&#34;https://en.wikipedia.org/wiki/Infrastructure_as_code&#34;&gt;IaC&lt;/a&gt; or test data in the repository.&lt;/p&gt;&#xA;&lt;h2 id=&#34;sample-repository&#34;&gt;Sample repository&lt;/h2&gt;&#xA;&lt;p&gt;To demonstrate the problem, here&amp;rsquo;s an example repository: &lt;a href=&#34;https://github.com/majk-p/nice-pr-diffs&#34;&gt;https://github.com/majk-p/nice-pr-diffs&lt;/a&gt; that features two PRs:&lt;/p&gt;&#xA;&lt;p&gt;The first one is hard to read &lt;a href=&#34;https://github.com/majk-p/nice-pr-diffs/pull/1/files&#34;&gt;https://github.com/majk-p/nice-pr-diffs/pull/1/files&lt;/a&gt; because it features a wall of text - new testing data that has been added.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
