Kode

Connect your GitHub account

So the code shows up inside Projekt Republic instead of being hunted down.

How to do it

1. Open the organization settings and look for the GitHub block.
2. Authorize through GitHub, which is the recommended route, or paste a read token.
3. The token is stored encrypted on the server.

How to undo it. Disconnecting deletes the stored token and turns off the activity feed in every project.

Check what Projekt Republic touches in your repositories

To know, before authorizing, what gets read and what is never written.

How to do it

1. The connection card lists what this access does: read your repositories, read the activity of the linked ones and read reviews.
2. Projekt Republic never writes to GitHub: it does not open issues, comment on pull requests or push code.

Link a repository to a project

So that project shows the commits and pull requests of that repository.

How to do it

1. Go into the project and open its GitHub section.
2. Pick one of the repositories the connected token can reach.
3. A single project accepts several linked repositories.

How to undo it. Unlinking removes the repository from that project and touches nothing inside GitHub.

Explore a repository in Kode

So you can read a project’s code without going out to GitHub.

How to do it

1. Open Kode: the sidebar lists the repositories you can see, grouped by project.
2. Pick one, open folders in the tree and click a file to read it; switch branch or tag at the top.
3. Click a line number (with Shift, a range) and copy the link to send it to someone.

Search code across every repository

So you can find where something is used without knowing which repository it lives in.

How to do it

1. In Kode, open search, type the text and click “Search”.
2. Filter the results by repository, extension or path.
3. Each search uses between one and three of the organization’s 10 per minute.

Link a commit to its task

So the work hangs from whatever asked for it, without touching anything here.

How to do it

1. Write the task key in the commit message or in the pull request title: “PJKT-142”.
2. The key is the project key plus the task number, and lowercase works just as well.
3. When the branch is pushed, the task picks it up on its own.

Read a pull request without leaving

To see what changed and what was said while you look at the task.

How to do it

1. Open the task and scroll down to its development section.
2. Open the linked pull request: the changes and the review comments are there.
3. It is read-only here; to answer a comment, go to GitHub.

See how long delivery takes

To know whether what gets opened ends up closed, and how long it took.

How to do it

1. At the top of the project GitHub section sits the average delivery time.
2. Next to it goes how many pull requests were merged, and the card itself states which time window it covers.