Expose Version Control REST API endpoints to allow for CI automation

[yaustar]

For some workflows where developers have code in separate version control repo, having the API endpoints would really help with automation of workflows.

• [ ] Create checkpoints
• [ ] Switch branches
• [ ] Merge branches - option to merge if there are no conflicts
• [ ] Create branches
• [ ] Close/Open branches
• [ ] Get checkpoints from a branch
• [ ] Get checkpoint data (message, changed files etc)

[yaustar]

From #539

• Fetch list of projects with ids
• Authenticate a user and get an access token in return
• Make checkpoints
• Switch branches
• Merge branches

[yaustar]

Related thread: https://forum.playcanvas.com/t/switching-branches-via-nodejs/22446

[yaustar]

Thinking on this a little more:

• Create checkpoints
• Switch branches
• Merge branches - option to merge if there are no conflicts
• Create branches
• Close/Open branches
• Get checkpoints from a branch
• Get checkpoint data (message, changed files etc)

Is there anyway we can do a merge preview where a 'diff' could be downloaded? Could we utilise the PlayCanvas Editor diff viewer to be able to load the diff file directly?

[dfrancos-hub]

Hi, I think it makes sense to expose also a create project endpoint to allow a full cicle from creating/editing/downloading the app. Thanks in advance

[yaustar]

@dfrancos-hub Can you create that as a new request please as that endpoint isn't part of version control :)

[pensan]

From #539

• Fetch list of projects with ids
• Authenticate a user and get an access token in return
• Make checkpoints
• Switch branches
• Merge branches

"Fetch list of projects with ids" should probably not be part of this Version Control task but rather it's own issue.

Allowing GET https://playcanvas.com/api/projects to return a list of all projects accessible by the given user-/organization-token.

This would be useful outside of the Version Control system.