Working with projects
This area leads from discovering a project to submitting a change. It assumes no knowledge of namespaces, permission files or the connected source control system.
Getting started
Quickstart: from project to source — the shortest way to a first result, in three steps, without Git.
Find a project → Find a repository → Browse source → clone → Submit a change
Common tasks
Structure
| Region | What happens there |
|---|---|
| 1 | The entry point. Names how many projects and repositories this account may see, and carries both lists with search and filters. |
| 2 | The repository table across all projects — as part of the entry point, or on its own where only the repository name is known. |
| 3 | A repository with file tree and lists of branches and tags. |
| 4 | The routes to the source: archive, Git, development environment. |
| 5 | The way from “may read” to “may contribute”. |
Key features
- Project overview with search, status filter and your own role per project.
- Cross-project repository list, filtered by what your own account may see.
- Source view in the browser with branch and tag selection, without a local installation.
- Archive download as a ZIP file for everybody who does not use Git.
- Git access through an endpoint of the wiki, with a personal access token.
- A structured request for contributor rights instead of an instruction to go and find somebody.
The underlying idea
A project is a working area with a key of its own. A person's role applies to the whole project, not to the single page, and a repository inherits the permission of the namespace it hangs on. There is therefore no second permission system beside the wiki's own.
In full: How a project is built describes the areas, Visibility and permissions what follows for lists and numbers, Contributing the ladder of roles.
Administration
Managing the connections and mounts belongs to the wiki administration; the project pages themselves are written by the people working on the project. Mounting a repository also sets the permissions of its namespace. How a new project is created is in Create a project.
Troubleshooting
- Look up a fault (German) — search for the message on your screen, word for word
- A page or a repository turns me away (German)
- Clone fails or push is refused (German)
For developers
- DevOps Core (German) — project, role and navigation model
- ADO-Git plugin — repository mounting and the Git endpoint
Related topics
- Projects and repositories (German) — the entry point that answers both questions
- Repositories — the repository table alone
- Visibility and permissions — what the numbers mean
- How a project is built — the areas of a project
- Where documentation belongs — repository or wiki, and in which language