Update GitOps repository

Updates files of a GitOps repository either by pushing changes directly to a given folder of a given branch or by opening a pull request to it. URL of the pull request is exposed as an output in the latter case. Updated files are go templates rendered by substituting given values. A Github username and Personal Access Token must be provided with access to the repository.

How to test this Step

0. Clone this repo
1. Set up .bitrise.secrets.yml file with the following content:

envs:
  - DEPLOY_TOKEN: YOUR PAT
  - MY_STEPLIB_REPO_FORK_GIT_URL: YOUR FORK HTTP URL OF THE STEPLIB REPO

2. Export these variables in your terminal
   • $DEPLOY_USER: your GH username
   • $DEPLOY_REPO_URL: Where to test commit, e.g. https://github.com/bitrise-io/sandbox-deployments.git
   • $DEPLOY_PATH: An existing folder in that repo, e.g. zsolt-test
3. Run bitrise run test which will open a PR
4. Confirm the PR is opened but close it

How to release

1. Merge the PR
2. Create a new release / tag
3. Fork the steplib https://github.com/bitrise-io/bitrise-steplib
4. Set YOUR fork steplib URL in the secrets file (see above)
5. Export the step version $BITRISE_STEP_VERSION in your terminal, without the prefix v
6. Run bitrise run share-this-step
7. Go to your forked steplib and create a PR
8. Get someone to review your PR and merge it