21 Mar, 2013
2 commits
-
Capistrano: deploy from fixed branch
-
Not the 'current' branch in the local clone fo the repo. I feel like deploying from the current branch in the local clone is a bit presumptous. I expect most people want to deploy from one branch while allowing for development of several feature branches. Right now you always have to remember to check out master before deploying or you may deploy your feature branch (which may not even be pushed).
12 Mar, 2013
1 commit
12 Feb, 2013
1 commit
08 Feb, 2013
1 commit
05 Nov, 2012
1 commit
29 Aug, 2012
1 commit
-
…gn to show delete 'X' at right, and gravatar at left
28 Aug, 2012
1 commit
05 Jun, 2012
1 commit
-
… issues for public/private/no repos)
02 Jun, 2012
1 commit
01 Jun, 2012
1 commit
23 Mar, 2012
1 commit
27 Jan, 2012
1 commit
06 Jan, 2012
1 commit
10 Sep, 2011
1 commit
06 Sep, 2011
1 commit
02 Sep, 2011
2 commits
-
… are now stored in an automatically created app called 'Self.Errbit'.
-
… them locally, in an automatically created App named "Self.Errbit". Errbit can still be configured to send errors to our central Errbit instance, but we were getting too many spam errors caused by users (e.g. invalid email address). Most developers will prefer to see Errbit's errors themselves anyway. I will write up a HowTo on how developers can configure a GitHub issue tracker for 'Self.Errbit', in order to send us error reports.
27 Aug, 2011
1 commit
15 Aug, 2011
1 commit
-
…e by default, but this can be changed in config.yml [ci skip]
11 Aug, 2011
2 commits
-
…y need for migrations, and I made my implementation as unintrusive as possible. Some organizations (such as ours) will find the "username" field useful when implementing an alternative authentication strategy. (Default is off, and this is fully backwards compatible.)
07 Aug, 2011
2 commits
-
…f both low and high traffic sites, so this feature would be useful so that we can stay on top of errors in some cases, and avoid getting spammed in others.
24 Feb, 2011
1 commit
15 Aug, 2010
1 commit
