Browse source
Situation
You want to look into a repository's source without installing Git or downloading anything.
Approach
Every mounted repository has a screen of its own with a file tree and lists of branches and tags. The content is read live from the connected system on every call; the wiki holds no copy.
Procedure
- Open Repositories and choose the repository you want.
- The Code tab shows the file tree of the current branch. Clicking a folder expands it in place; its contents are fetched then, and the page is not rebuilt.
- Clicking a file opens its content for reading, syntax-highlighted. Where the source viewer is absent from an installation, the tree stays walkable and files cannot be opened.
- Through Branches or Tags you choose another revision. Clicking an entry returns to Code, pinned to that revision.
- The header names project, repository, visibility, your role and the revision shown.
The chosen revision is in the address. A link to a particular branch therefore stays valid and shows every person the same revision.
Remarks
Every repository has an address, even without a wiki page of its own. The screen is called through the namespace the repository is mounted on, and can be bookmarked:
?do=wkdoadogit_repo&ns=code:dokuwiki-plugins:wkdoadogit&ref=main&tab=code
ref pins branch or tag, tab chooses between code, branches and tags. Both may be absent; the default branch and the Code tab then apply.
Which files you see is decided by the ACL of the namespace the repository is mounted on — not by a licence of the source system.
Visibility and role stand side by side in the header because only together do they say what the screen permits: visibility belongs to the repository, the role to you.
There are no tabs leading nowhere. Where an area does not appear, it is absent from this installation — it is not greyed out for lack of permission.
Every call is an access to the source system. The tree keeps no stock: an expanded folder and an opened file are fetched at that moment. A page with many embedded excerpts pays that correspondingly often.
Related topics
- Embed source in a wiki page — when the excerpt belongs in a documentation page