Always Display the Latest Version of a File

By default, the web interface links to files use a specific commit hash. This means the URL always shows a historical snapshot, not the most recent version. For documentation files, scripts, this is inconvenient — I usually want the latest state.

The last_commit_cgi tool solves this by dynamically resolving the most recent commit affecting a file and redirecting the request to it. As a result, you can publish stable links that always point to the newest content without manual updates.

Typical use cases include:

• Linking to a README from an external website
• Sharing a script that evolves over time
• Embedding live documentation in other pages

You can find details on my repository in the last_commit_cgi folder

A Practical Alternative to “got diff”

The second tool provides an alternative way to visualize differences between current file and his last commit versions. While Got offers diff capabilities, comparing revisions in a more specialized tool is some time easier.

The alternatif_diff utility retrieves the prior version of a file and produces a readable side-by-side comparison using external tools. This allows to use a tool like meld for example. But others could be added in the script too.

Simple Tools, Real Productivity

Neither tool adds complexity to the server, yet both remove friction from daily workflows. Together, they make a self-hosted Got environment far more convenient for browsing, sharing, and reviewing code — all while keeping full control over the infrastructure.

You can find details on my repository in the alternatif_diff folder