I have linked my CloudScript revisions to a GitHub repository as this is the way my company would prefer to maintain our scripts. The docs and forums seem to make it clear that new revisions should only be made when changes are made to the "master" branch of the repository. I created a second branch called "develop" to test this and found that a revision was made even when pushing commits to "develop" and not "master". Can someone help me understand if this is a bug or I'm doing something incorrect? All I did was click the add-on for GitHub and set the repository name. If PlayFab is going to make revisions for every commit we make to non-master branches, then we're going to end up with a bloated list of revisions with scripts we never plan on using.,
Reading through docs and forum questions it seems that CloudScript revisions are only supposed to be made when changes are made to the "master" branch of the GitHub repository linked to the PlayFab title. I created a second branch called "develop" in my repository to test this and found that a revision was still made when pushing only to the "develop" branch. Can someone help me understand why that is? I think my company would prefer to create our revisions through GitHub, but if revisions are going to be made for every commit we make to non-master branches then our revision list is going to get bogged down with scripts we never plan on using.