Repository is not updated by pushing content immediately after its creation
Repositories are not updated when changes are pushed into it immediately after their creation and the initial screen is always displayed. The content is only accessible after restarting Stash.
FIgure 1: initial screen example immediately after a repository creation.
Causes and Resolutions
Stash relies on hook scripts that are installed into each repository (and managed by the system) to provide change information that, in turn, allows it to update the repositories, pull requests and check branch permissions. If the hooks are not installed correctly, or are damaged, these required callbacks do not happen and the functionality associated with them fails.