See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope> is optional
If a project has to have multiple git repos (e.g. Bitbucket and Github) then it's better that they remain in sync.
Usually this would involve pushing each branch to each repo in turn, but actually Git allows pushing to multiple repos in one go.
If in doubt about what git is doing when you run these commands, just
| # @ https://cheat.readthedocs.io/en/latest/python/mock.html | |
| obj.call_count # number of times it was called | |
| obj.called == obj.call_count > 0 | |
| obj.call_args_list # a list of (args,kwargs), one for each call | |
| obj.call_args # obj.call_args_list[-1] (args,kwargs from last call) | |
| obj.return_value # set to what it should return | |
| obj.side_effect # set to an exception class or instance that should be raised when its called | |
| obj.assert_called() # doesn't work with autospec=True? just assert obj.called | |
| obj.assert_called_with(*args, **kwargs) # last call was with (*args, **kwargs) |