<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 21:31:58 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Content With Style: Quick lint check on changed php files with svn st and xargs]]></title>
      <guid>http://www.phpdeveloper.org/news/13409</guid>
      <link>http://www.phpdeveloper.org/news/13409</link>
      <description><![CDATA[<p>
On the Content with Style blog, there's <a href="http://www.contentwithstyle.co.uk/content/quick-lint-check-on-changed-php-files-with-svn-st-and-xargs">a "quickie"</a> you can drop into a subversion hook as a part of your check-in that will run the lint command on only the changed files (not your entire repository).
</p>
<blockquote>
If you haven't done it in a <a href="http://blueparabola.com/blog/subversion-commit-hooks-php">hook</a> already, here's the quick way to check all your changed files for syntax errors.
</blockquote>
<p>
This sort of command would be the most useful in a pre-commit hook to ensure that everything passes correctly. Their example only looks for ".php" files, but can be modified easily if you happen to use ".html" or another custom extension for your pages too.
</p>]]></description>
      <pubDate>Tue, 20 Oct 2009 08:27:24 -0500</pubDate>
    </item>
  </channel>
</rss>
