Skip to content

Rake task allows for a different commit message #408

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

Merged
merged 1 commit into from
Jun 2, 2025

Conversation

ghoneycutt
Copy link
Contributor

Without this commit, you cannot inform the rake task to push gh-pages to accept a different commit message. This is necessary in environment where commit messages have to be in specific formats.

None of the system calls were checking the exit status of their respective commands. Not stopping on error means that the rake take can fail and you and your pipelines would not know.

@ghoneycutt ghoneycutt requested review from bastelfreak and a team as code owners May 30, 2025 19:31
@ghoneycutt ghoneycutt marked this pull request as draft May 30, 2025 19:31
@ghoneycutt ghoneycutt force-pushed the configure_push branch 4 times, most recently from d720ad4 to fc267d0 Compare May 30, 2025 19:52
@ghoneycutt
Copy link
Contributor Author

I tested this works by configuring a rake task to use a different message as well as calling the normal rake tasks here and getting the default message as shown in ghoneycutt/puppet-module-pam#279

@ghoneycutt ghoneycutt marked this pull request as ready for review May 30, 2025 20:22
Without this commit, you cannot inform the rake task to push gh-pages to
accept a different commit message. This is necessary in environment
where commit messages have to be in specific formats.

None of the system calls were checking the exit status of their
respective commands. Not stopping on error means that the rake take can
fail and you and your pipelines would not know.
@gavindidrichsen gavindidrichsen merged commit a3fe160 into puppetlabs:main Jun 2, 2025
5 checks passed
@ghoneycutt ghoneycutt deleted the configure_push branch June 2, 2025 15:29
@ghoneycutt ghoneycutt restored the configure_push branch June 2, 2025 15:29
@ghoneycutt
Copy link
Contributor Author

@gavindidrichsen Could you please cut a release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants