Skip to main content
What you can do with branches depends on your role in the project. The rules are the same for the Frontend and for Logic services. A role that can work on the Frontend’s code can work on a service’s code, and a role that cannot, cannot.

Roles at a glance

A Viewer does not see branches or pull requests. They see “You don’t have access to the code. Branches and pull requests are visible to project owners, admins and editors.”

Who can publish and merge into protected branches

Publishing the Frontend and merging into a protected branch are the actions that change what other people use. The project-wide setting Who can publish controls who can do them:
  • Only Owners and Admins. This is the default. Editors cannot use Publish site or merge into protected branches.
  • Owners, Admins and Editors. Editors can do both.
Find the setting in the Settings tab of Manage branches in the Frontend. In a service, it appears on the Branches page. Only Owners and Admins can change it. The confirmation explains the effect: with Owners and Admins only, Editors can no longer use Publish site or merge into protected branches of the app and its services. The confirmation names only Publish site and merges into protected branches. It does not list deploying a service. Owners, Admins, and Editors can deploy a service. If you do not have permission, you see a message such as “Merging into a protected branch requires publish permission.” or “In this project only Owners and Admins publish and merge into protected branches.” Ask an Owner or Admin to do it.

Reviewing

  • You cannot approve, or request changes on, your own pull request. You can still comment.
  • Your approval counts while the branch has not changed. If new commits arrive, the approval is marked Outdated: new commits since and you review again.
  • Requesting Archie Reviewer consumes credits. See Archie Reviewer.

Next steps