Plan Ticket to PR
Changed onLists the factory Loops POST /experimental/projects/{projectId}/factory/ticket-to-pr would set up for the issue source, with the skill and triggers each one runs, so a client can show how they overlap the project's live Loops before setup. existingLoopId names the live Loop that already does a Loop's job, which setup leaves as it is. issueSource is the source setup would use, which is the source of the project's live ticket intake Loop when it has one: the oldest Loop whose triggers start on a GitHub issue label or a Linear issue delegated to Tessl. The GitHub label is the one setup would use before it checks the repository's spelling of it. otherProjectLoops lists the live event Loops of the other projects on the same repository that the caller can view, since one event from the repository can start one of them and a Loop setup plans.
Request
- Base URLhttps://api.tessl.io
- URLhttps://api.tessl.io/experimental/projects/{projectId}/factory/ticket-to-pr
- Authnone declared
Path parameters
Query parameters
Where issues come from. Defaults to Linear.
GitHub source only: the issue label.
Headers
Response
Default Response
Changes
- info
api operation id
getProjectFactoryTicketToPrwas added
- info
- info
added the required property
//to the response with the status
- info