Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different release-please configs in same repository and release from brach #1059

Open
raulmartinezr opened this issue Nov 25, 2024 · 0 comments
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.

Comments

@raulmartinezr
Copy link

raulmartinezr commented Nov 25, 2024

Thanks for stopping by to ask us a question! Please make sure to include:

- What you're trying to do
Configure multiple relsease please configs in same github repo using same branch (master) as target

- What code you've already tried

two base paths in repo (backend/cloud and backend/edge) with different configs and manifest

      - uses: googleapis/release-please-action@main # googleapis/release-please-action@v4
        id: release
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          config-file: backend/edge/release-please-config-backend-edge.json
          manifest-file: backend/edge/release-please-manifest-backend-edge.json
      - uses: googleapis/release-please-action@main # googleapis/release-please-action@v4
        id: release
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          config-file: backend/cloud/release-please-config-backend-edge.json
          manifest-file: backend/cloud/release-please-manifest-backend-edge.json

- Any error messages you're getting

Release PR are being overriden when action is triggered as both configuration uses the same branch release-please--branches--master. Would it be possible to use different configs with diferent PR branches but keeping same target branch?

@raulmartinezr raulmartinezr added priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue. labels Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

1 participant