snippet from update_branch() function:

        # set perms
        self.run_cmd('find {0} ' \
                     '-type f ' \
                     '-not -path *.git* ' \
                     '-exec chmod 644 {{}} ;'.format(fullpath))

        self.run_cmd('find {0} ' \
                     '-type d ' \
                     '-not -path *.git* ' \
                     '-exec chmod 755 {{}} ;'.format(fullpath))

Why do you change the permissions? Git only store the executable bit for files meaning we would ever end up with files that have '0755' or '0644'. Semi-Source

If there is a security concern about having files with the executable bit, perhaps an option should be created such as 'noexec'. If noexec is true, then we could call find to strip executable bits.

Text parsing depends on banners being off, bad for gitlab which can easily have banners

Right now if the key is unreadable it is a silent error or misleading error at least

Similar to what is done in _initial_checkout function with try/except. There is now some common code that could be refactored into one get_list_of_remote_branches function.

If you git server displays an ssh banner after login, this code currently chokes.

Sometimes the branch checkout directory goes foobar and repowatch cannot handle the failure scenario. What ends up happening is a vague git fetch command failed.

Action list: create, update, delete