Allow to release to a different repository

[prsnca]

Adds support for the case mentioned in this issue - #194

Thanks!

[cpanato]

@prsnca do you have an example workflow run for this case?

[prsnca]

@cpanato, I have been using my fork (https://github.com/prsnca/chart-releaser-action) for these purposes.
we have a release workflow (triggered when a new tag is pushed) in a private repository which checks out the public repository (https://github.com/snyk/runtime-sensor) and releases the chart to both.
I can share here the snippets from the workflow:

...
steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Checkout runtime-sensor public repository
        uses: actions/checkout@v4
        with:
          repository: snyk/runtime-sensor
          path: runtime-sensor
          token: "${{ secrets.RUNTIME_SENSOR_GITHUB_TOKEN }}"

      - name: Get Latest Tag
        id: get-tag
        ***
...

      - name: Create tag in public repository
        run: |
          cd ${{ github.workspace }}/runtime-sensor
          echo "RUNTIME_SENSOR_HASH=$(git rev-parse HEAD)" >> $GITHUB_ENV
          git tag ${{ steps.get-tag.outputs.tag }}
          git push --tags --porcelain

      - name: Run chart-releaser for public repo
        uses: prsnca/chart-releaser-action@v1.6.2
        with:
          repository: snyk/runtime-sensor
          commit: ${{ env.RUNTIME_SENSOR_HASH }}
        env:
          CR_TOKEN: "${{ secrets.RUNTIME_SENSOR_GITHUB_TOKEN }}"

      - name: Run chart-releaser for own repo
        uses: helm/chart-releaser-action@v1.6.0
        env:
          CR_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
...

[YanishR]

What's the status on getting this merged? I see this was a feature previously. Is there any alternative on how to push to a different repo?

[markgoddard]

I'd love to see this feature!

[markgoddard]

I tried this locally and it didn't work for me. First, the new input isn't included in action.yml, so it can't be used.

I think this may work for the use case described in the issue, publishing a private repo to a gh-pages branch in a public repo. But I couldn't get it to work for my use case, which is releasing to the local repo, but updating the index.yaml in a remote repo.

[markgoddard]

I tried this locally and it didn't work for me. First, the new input isn't included in action.yml, so it can't be used.

I think this may work for the use case described in the issue, publishing a private repo to a gh-pages branch in a public repo. But I couldn't get it to work for my use case, which is releasing to the local repo, but updating the index.yaml in a remote repo.

I've proposed a fix for the input issue: prsnca#4

[prsnca]

@markgoddard - I approved your fix, thanks!
@cpanato - can we get this merged? 🙏