Problem: Currently when looking at commits, the hash is in the title with big blue letters, while the commit message is below.

Possible solution: While I don't object to having the hash first, I think ideally the format should be:

[commit message] - [user] [hash]

The commit message being in the title.

Problem: Can't restrict users from committing to a specific branch.

Solution: Add per branch restrictions Github's approach: https://help.github.com/articles/about-branch-restrictions/

Problem: Repo's don't require users to sign commits.

Solution: In a repo's setting page or in the creation of a new repo, specify if repo is signed only.

Problem: Web interface doesn't show if commits, tags, or merges are signed.

Solution: Add a verified or signed icon next to each object that supports it. Github does it this way: https://github.com/sublimehq/sublime_merge/issues/url

Optional: Implement signing verification with user supplied gpg key. So this verifies that the user pushing the change is actually the specified user.

Also, switching to a branch should direct the user to the summary page instead of the tree page.