Attach your project

Your project is a folder in a repository. Attaching it gives it a place in your company catalogue, where your team reads its requests without cloning anything. You do it once, from Ryno, and your repository carries the result to everyone else.

Before you start

Attaching needs you signed in with your work account, because a project belongs to your company and the service has to know which one. If you are not signed in, the box reads Sign in to attach this project, with Sign in… beneath it. That button takes you to the Account pane of Settings. Sign in there, then open the box again.

If your account is not part of a company yet, the box says so when you select Attach, and nothing is created. A project is attached to a company, not to a person, so ask whoever runs your Ryno service to set your company up, then attach again.

Attach your project

Open the workspace menu at the top of the window and choose Attach to company workspace…. The same box opens from Settings: in the Workspace pane, the Company workspace row has an Attach… button.

Both are there only for a folder you opened from disk. A workspace you read from the company catalogue is already attached to it, so there is nothing to offer.

The box asks for a Project name, filled in from the name of your folder. Change it if your team knows the project under another name, then select Attach.

What Ryno writes in your repository

Once the project is attached, Ryno writes its identifier in .ryno/config.json, under catalog.projectId. Nothing else in the file changes. Commit that file and push it.

That is what keeps your team to one project. When a colleague pulls the file and opens the repository, Ryno reads the identifier it finds there: the box reads Attached to your company workspace straight away, and there is nothing to attach. Leave it at that. The Regenerate token… button it offers is not for getting a token of your own: it replaces the one your pipeline uses, and the team’s publish job fails until someone updates the variable.

A colleague whose copy does not carry the file yet can still attach the project. Ryno recognises the same repository, and the service answers with the project that already exists instead of creating a second one. The box then tells your colleague who attached it first, and when.

If Ryno could not write the file, the box tells you so, and nothing is lost: keep the token it shows, and attaching again finds the same project.

Keep the token, it is shown once

Under Attached to your company workspace, the box hands you a project token and the job your pipeline needs, in three steps: Add the token to your CI/CD variables, Add the publish job and Merge to your default branch. The next page walks through all three.

The token lives in that box and nowhere else. Ryno does not keep it once the box closes, and the service stores only a fingerprint of it, so nobody can show it to you again. Copy it before you close the box. If you try to close the box without copying it, Ryno asks Close without copying the token? and reminds you that You won't see this token again.

A colleague who attaches a project somebody else created gets no token. It belongs to the person who created the project, and it is already in your pipeline’s variables.

Regenerate a lost token

If the token is lost, or has ended up somewhere it should not be, open the box again and select Regenerate token…. Ryno asks Regenerate the project token? first, and says what follows: The current token stops working now. Pipelines using it fail until you update the variable. Confirm with Regenerate token, copy the new token, and paste it into the RYNO_PROJECT_TOKEN variable of your repository.

What stays on your machine

Ryno names the project after your folder, never after the address of your repository. That address does not leave your machine: to recognise the same repository when a colleague attaches it, Ryno sends a fingerprint of it, which tells the service that two copies are one without saying where either of them lives. What reaches the service is the name you chose, and later, from your pipeline, the shared part of .ryno/.

When the project was removed

An administrator can remove a project from the company workspace. If that happened to yours, Ryno tells you once a publication from this repository is refused: the workspace menu then says the project was removed and offers Attach again, and the Workspace pane tells you who removed it and when. Any member can use it, not only an administrator. It attaches the repository as a new project, with a new token to keep and to paste into your pipeline’s variable, because the old project and its token are gone for good.

Remove a project tells the whole story: who can do it, what disappears and what stays.