Hexis Files

What's new

Three ways to have your repository. The setup screen now offers a choice of where your knowledge, skills and tools are kept:

• Managed for you. Hexis keeps the repository itself, with its backups. Nothing to enter, so a new deployment can finish setup in one press.
• GitHub. Connect a repository through a GitHub App, which Hexis registers for you and you install on the repository. No access token is created or stored. You can connect a repository your own GitHub account can write to.
• Address and token. Any git host, as before.

A deployment that is already set up stays as it is. See docs/repository.md.

A shorter first run. First-time setup asks for two things: the repository and single sign-on. Audit log and Marketplace settings stay on the Deployment page.

Ask for access where you need it. Someone who can only read a file or folder can ask for Can edit or Owner from its Manage access dialog, with an optional note. The people who can already edit it accept or decline in the same dialog. A request closes by itself once the person holds the level they asked for.

Change requests open at once. A change request shows its files immediately. It is checked against the latest shared version only when that version changed one of the files the request changes.

Authors can delete their own change requests. The author of a request can delete it, as admins could. Owners of the changed files keep Decline.

Fixed

• A deployment whose repository address changed recovers on its own and loses nothing. A working copy of the same repository at a new address is kept, unpushed work included. A working copy of another repository is moved to replaced-working-copies/ in the backups volume, never deleted.
• A change request whose push had failed is retried the next time it is opened, and a pull no longer drops the shared version out of a request's history.
• A tool call that names no branch is refused with a message that says which input is missing. It no longer acts on a branch called undefined.
• A branch name that was never cloned answers "there is no branch" on every attempt, not "no longer exists" after the first.
• The tool page's menu lines up with the plugin and skill pages.

Upgrading

Nothing is required of an existing deployment. It keeps the repository it has.

To move to another repository, open its tab on the Deployment page, confirm, and restart. The move takes effect at the restart. The repository you leave is untouched.

A managed repository is stored in the backups volume. Back that volume up.

For overlays built on the @bevel-software/platform-* packages

• IWorkflowService gains a required method, latestClosedChangeRequest.
• JoinRequestsService takes the access-control service as a fourth constructor argument, and its list and reconcile take an AccessRequestTarget.
• pendingProposals takes a fourth argument and returns null when the branch's copy is missing or unreadable.
• AccessRequestsBanner moved to the access module and takes itemName.
• PullRequestDetail gains two required fields, viewerCanDelete and viewerIsAuthor.
• CoreServices gains repositorySource, managedRepository and githubApp. Read the repository's address from repositorySource.url(): the stored address is empty on a managed or GitHub deployment.
• AuthService.loginWithSso takes an optional { admittedByProvider: true }, for a sign-in provider that decides admission itself.
• The app registry gains two slots, deploymentPanel and signInOption.