​
Connecting your tools

  1. Sign up or sign in to the Saldor Console
  2. Follow the onboarding steps to connect your GitHub account.
  3. If you use Linear, connect your Linear account. You can always do this later, and just stick with Github issues for now.

​
Putting Saldor to work

In Github Issues, you should see a new label with the name “saldor”. That is the label you will add to tickets that you want Saldor to work on. Or in Linear, in place of labels, you should assign the Saldor user to the ticket.

​
Now what?

You can always check the status of Saldor’s work in the Console. Saldor may ask clarifying questions on the ticket itself before creating a PR. In this case, anyone on your team can respond to the question (no @saldor tag required) and it will either continue or ask a follow up question.

​
Once the PR is created

Once Saldor has created a PR, you can review it in the same way you would any other PR. If you have any feedback, you can add single comments on individual lines, or on the PR itself (what Github calls issue comments), or as part of a “review”. The only type of Github comment that we don’t currently support is a “commit comment”, which is a comment on a particular commit of the Github PR. If you don’t know what this is, you likely don’t use this Github feature.

Saldor will monitor the PR for any failed CI/CD workflows, and evaluate if it is within it’s purview to fix. This capability is still in beta.

​
Present Limitations

Saldor is currently sightless - it doesn’t have an ability to understand images that you post in Linear or Github. Additionally, it can’t run a frontend service and see it’s output in a browser as a human developer might. We still use it for small frontend bugs that are well scoped, but it’s not yet ready for larger frontend work.

​
Dealing with failure

If you are seriously unhappy with Saldor’s work on an issue and unable to guide it with your comments, you can close the PR (which should remove the “saldor” label from the ticket). You may want to udpate the ticket with more context on what you’re looking for, then you can then relabel the ticket with Saldor, and it should create one anew.

If you ever see a job in a “failed” state on the dashboard, please reach out to us (either in your shared slack channel or at support@saldor.com). Or as above, try closing the PR (if it exists) and unlabeling (unassigning) and relabeling (reassigning) the ticket with “saldor”.

If you have any feedback, please reach out to us at support@saldor.com. We’d love to hear from you!