I’ve created a pull request with small fixes to the Aiyagari transition example 
Mostly to practice with git and PR, but I did fix two bugs: a typo in the comments and simoptions being missing from the call of the function StationaryDist_Case1.
Seen and merged
You set it up nicely 
(I’m still getting the hang myself of not being the only git user for the toolkit, but I’m progressing)
1 Like
This time I managed not to mess things up. Issue will arise when you update the master on your git. In that case my fork will not be automatically updated…
One of the tricks I learned the hard way is to always do development on a feature branch, not the main branch. Of course when accepting a pull request, that updates the main branch. And of course when looking at the main branch, we inevitably start making changes to files that, for a moment, appear to git like changes to the main branch. But if you then create a branch AND PORT YOUR CHANGES TO THE NEW BRANCH, then when you are done with your changes, you can make sure you are up-to-date with the main branch and then issue a clean pull request.
When making changes directly to the main branch, without the insulation of a feature branch, you are very much on your own, for better or worse.
2 Likes
I think this is what I did, but I will check to be sure