Update JamesIves/github-pages-deploy-action action to v4.2.5#35
Merged
marcospassos merged 1 commit intoMar 14, 2022
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.1.3->v4.2.5Release Notes
JamesIves/github-pages-deploy-action
v4.2.5Compare Source
Minor Changes
v4.2.4Compare Source
Minor Changes
v4.2.3Compare Source
Minor Changes
v4.2.2Compare Source
Minor Changes
JamesIves/github-pages-deploy-action@v4if you'd like to always have the most cutting edge changes outside of using the release branch directly.vto be consistent with other officially provided actions by GitHub. You can useJamesIves/github-pages-deploy-action@v4.2.2for instance. Dependabot should pick up this change automatically.v4.2.1Compare Source
Minor Changes
v4.2.0Compare Source
Happy New Year 2022!
Minor Changes
git mvcommand prior to the workflow running. (#895)single-committo fail when usingrepository-nameif the branch name was equal from the origin to destination. (#665)v4.1.9Compare Source
Minor Changes
v4.1.8Compare Source
Minor Changes
New Contributors
Full Changelog: JamesIves/github-pages-deploy-action@4.1.7...4.1.8
v4.1.7Compare Source
Minor Changes
npm ciinstead ofnpm installin examples by @bananer in use "npm ci" instead of "npm install" in examples JamesIves/github-pages-deploy-action#934git-config-emailoption again. If you wish to omit this field entirely you must now provide<>in the field instead of an empty string. This is due to the fact that GitHub Actions defaults all undefined fields to an empty string, causing the default behavior to not work when you don't provide agit-config-emailparameter at all. You can find an example of this below.New Contributors
Full Changelog: JamesIves/github-pages-deploy-action@4.1.6...4.1.7
v4.1.6Compare Source
Minor Changes
git-config-emailoption now accepts an empty string as a valid value in a workflow. This will allow the email part of the commit signature to empty, for exampleAuthor Name <>. You can find an example of how to utilize this below. #868v4.1.5Compare Source
Minor Changes
v4.1.4Compare Source
Minor Changes
Configuration
📅 Schedule: "before 4am every weekday" (UTC).
🚦 Automerge: Disabled due to failing status checks.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.