Git Wiki Pages

A git wiki page is a wiki page whose type has been set to Git Repository. Once a page has this type, the folder that holds the page's resources also serves as a bare git repository that people can clone from and push to over the web using an ordinary git client. The settings in this fieldset control how new git wiki pages start out and how large the data pushed into them is allowed to be.

Who may create one

Turning a wiki page into a git repository is not offered to everyone. It is controlled by a modifier on the Feed and Wiki activity in Manage Roles. A role that carries the no_git_repository modifier cannot create git wiki pages. Out of the box the Admin role can create them and the ordinary User role cannot. To let another role create git wiki pages, remove the no_git_repository modifier from its Feed and Wiki activity; to stop a role, add the modifier.

Default Branch

The branch name a brand new git wiki page starts its empty repository on, for example master or main. This only affects repositories created after the setting is changed; repositories that already exist keep the branch they were made with.

Size caps

The three size caps limit how much data a client may push. Each is chosen from a dropdown offering sizes suited to project scales from Micro up to Extra Large, plus Unlimited which turns that cap off. Sizes are written in metric units, so 10M is ten million bytes and 1G is one billion bytes.

• Max Object Size — the largest a single object, such as one committed file, may be. Hosted services commonly cap individual files at around one hundred megabytes; a smaller cap keeps oversized files out of the repository.
• Max Push Size — the largest a single pack a client sends in one push may be. This bounds how much can arrive at once.
• Max Repo Size — the largest the repository as a whole may grow to. Once a repository reaches this size, further pushes that would grow it past the limit are refused.

A push that breaks any cap that is switched on is refused and the client is told the payload is too large. Leave a cap on Unlimited to impose no limit of that kind.

Suggested scales

The dropdown choices follow rough project scales:

• Micro — tiny repositories, a handful of small files.
• Small — a typical small project or document set.
• Medium — an active project of moderate size.
• Large — a substantial project, near the file limits common on hosted services.
• Extra Large — a large project that pushes a lot of data.

Pick the scale that fits how the repositories on this server are expected to be used. Because this server does not use large file storage, keeping the caps modest helps clones and pushes stay fast.