In order to keep your git environment in a good shape you need to clean up branches from time to time. It is especially difficult in case of build servers which complete pull requests on behalf of developers (like VSTS). It’s easy when you have just a few branches to review, but if you forget to do some cleaning for longer while then it’s getting painful. For sure you do not want to remove effects of your work by accident during cleanup.
Strona głównaUżytkownik
https://chrisseroka.wordpress.com/ | użytkownik
Staram się automatyzować wiele rzeczy. Build skrypt przechodzący lokalnie i na serverze po każdym commit’ie to podstawa. Można to w prosty sposób zrobić. Jest jednak część rzeczy, które są zbyt trudne do automatyzacji, albo po prostu nie da się ich zautomatyzować. ...
Sztuka programowania 2600 dni, 9 godzin, 33 minuty temu 113 źrodło rozwiń
How many times you've been thinking about better organization of your daily work? Starting from really basic stuff like tea time ending with automatic scripting work repeated frequently. Let me share a short list of improvements I've found thinking on that. Maybe you've got some other ideas?
Sztuka programowania 3500 dni, 21 godzin, 40 minut temu 351 źrodło rozwiń
The article describes a simple solution to log client side JavaScript errors together with back-end exceptions. No additional library is needed, although ELMAH is handy at this point
Ask yourself a question if your unit test project is a mixture of test methods or it shapes a specification that you can share with your client. If you really want to improve your testing experience look at NSpec.