Skip to content

Conversation

@h-haaks
Copy link
Contributor

@h-haaks h-haaks commented Aug 22, 2025

I'm currently trying to use these workflows in our private github repos where we require commits to be signed.
This PR allow setting the 'sign-commits' input of peter-evans/create-pull-request.

@h-haaks h-haaks force-pushed the allow-signing-commits branch from b374891 to 9798ac6 Compare August 22, 2025 08:16
commit-message: "Release ${{ inputs.version }}"
branch: release-prep
delete-branch: true
sign-commits: ${{ inputs.sign-commits }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q: Given the github_pat secret is required, and passed to the token, can't we just hardcode this parameter to true?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if a PAT works at all really, because there is no way store a private key on a regular user.
My thought was to keep this default false for now, and then we could try to replace secrets.PCCI_PAT_RELEASE_PREP with secrets.GITHUB_TOKEN in one of the voxpupuli module repo workflows.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have tested ( in my private repo workflow ) that this workflow can be used with app tokens. That's why I changed the decription of 'github_pat'.

@h-haaks h-haaks requested a review from smortex August 25, 2025 08:14
@h-haaks
Copy link
Contributor Author

h-haaks commented Aug 29, 2025

Using app tokens in reusable workflows is not as straight forward as I thought ...
I'm playing around with this to see if I can figure out the best way to handle this.

@h-haaks h-haaks marked this pull request as draft August 29, 2025 09:27
@h-haaks h-haaks force-pushed the allow-signing-commits branch 3 times, most recently from 8a41932 to 83da066 Compare August 29, 2025 09:48
@h-haaks h-haaks force-pushed the allow-signing-commits branch from 83da066 to 5cd8ae0 Compare August 29, 2025 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants