StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIs there a better way of writing a git pre-commit hook to check any php file in a commit for parse errors?
primarykey
Id
43374
data
AcceptedAnswerId
3069175
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-09-04T08:59:31.137
FavoriteCount
1
LastActivityDate
2018-02-09T06:46:11.553
LastEditDate
2008-10-06T10:41:54.007
LastEditorUserId
123
OwnerUserId
4342
ParentId
0
PostTypeId
1
Score
7
ViewCount
1400
LastEditorDisplayName
Prakash
text
Body
<p>What I have so far is </p> <pre><code>#!/bin/sh php_syntax_check() { retval=0 for i in $(git-diff-index --name-only --cached HEAD -- | grep -e '\.php$'); do if [ -f $i ]; then output=$(php -l $i) retval=$? if [ $retval -gt 0 ]; then echo "==============================================================================" echo "Unstaging $i for the commit due to the follow parse errors" echo "$output" git reset -q HEAD $i fi fi done if [ $retval -gt 0 ]; then exit $retval fi } php_syntax_check </code></pre>
Tags
<php><git><version-control>
Title
Is there a better way of writing a git pre-commit hook to check any php file in a commit for parse errors?
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USprakash
UserOwnerUserId
1. USRodney Amato
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
  singulars
  LinkTypeLinkTypeId
  LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
3. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  POIs there a better way of writing a git pre-commit hook to check any php file in a commit for parse errors?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  POIs there a better way of writing a git pre-commit hook to check any php file in a commit for parse errors?
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
3. VO
  singulars
  PostPostId
  POIs there a better way of writing a git pre-commit hook to check any php file in a commit for parse errors?
  UserUserId
  USprogram247365
  VoteTypeVoteTypeId
  VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.