From e69257aeed505f74f773a286939fb083cc6466a3 Mon Sep 17 00:00:00 2001 From: Adam Ormsby Date: Sat, 21 May 2022 14:21:44 +0700 Subject: [PATCH] update readme --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d9b77b0..60de18b 100644 --- a/README.md +++ b/README.md @@ -6,9 +6,9 @@ An action with forks in mind! Automatically sync a branch on your fork with the **Bonus:** This action can also sync between branches on any two repositories. So you have options. :slightly_smiling_face: -**\*\*FIXED in v3.2:\*\*** Checking for new commits to sync has been improved to better support active development branches. Instead of only comparing head SHA values, it does a deeper hash comparison between the target and upstream branches since the last action run. Length of time is based on new input var `shallow_since`, which defaults to `1 month ago`. ([wiki](https://github.com/aormsby/Fork-Sync-With-Upstream-action/wiki/Configuration#advanced-use)) - -**\*\*NEW in v3:\*\*** Test Mode runs key checks on your input values to help you verify your action configuration before running and avoid errors when you go live! ([wiki](https://github.com/aormsby/Fork-Sync-With-Upstream-action/wiki#test-mode)) +**\*\*FIXED in v3.3:\*\*** +- Changed variable name to match the docs -- INPUT_TARGET_PUSH_ARGS ---> INPUT_TARGET_BRANCH_PUSH_ARGS +- Output for `has_new_commits` is now properly set if fetching from upstream results in error Buy Me A Coffee