Update @ 2015-09-23: Frank suggested using incron to execute the sync base on file changes instead of time periods. Thanks!.
Whenever you have edited any page on Gollum, it will committed to the local repository which is checked out on the server. These commits WILL NOT be pushed to the Git Server. Similarly any push to the Git server will not sync to the repository running Gollum as it won’t execute git pull neither.
You may think of using the Git post-commit hook to trigger the synchronization whenever a commit is done but Gollum run Grit as the Git adapter and Grit doesn’t support hook.
A workaround suggested by Rod Hilton is to setup a cronjob and keep running the git push and pull on the server running Gollum.
Gollum is a simple documentation app base on Git. I could write the docs in markdown and all changes would be governed by the Git repository.
But the application doesn’t support any authentication and that means there is no way to trace who has committed the code.
Kudos to Stephanie Collett who wrote a rackup file for Gollum such that it will prompt for user email before the user start editing. That email is stored in session and would be used as identifying during commit.
It’s not easy to view the Git log in command line but most of the time is the most straight forward way or sometimes, the only way you could view the Git commit history.
Tig is a ncurses-based interface to view your Git repository.
We can always use the .gitignore to exclude files which we do not want to check in into the repository. But sometimes the repository is only read only and you dun want your files to be appeared in the git status command. A simple solution to exclude those files in your current working copy. This could be done by editing the .git/info/exclude. Here is an example for my Drupal 8 installation.
This speech was done by the Zach Holman, the Director of Design in GitHub. He talked about how GitHub starts from the very beginning and moves forward with progressive change. He also emphasized the automation in development, deployment and recovery is one of the key factors on the success of GitHub. The last but not least, in the past 5 years, no one ever quits GitHub. Love it!