search

aormsby / Fork-Sync-With-Upstream-action

An action to automatically update your fork with new commits from the upstream repo
MIT License
258 stars 70 forks source link

shallow update not allowed #66

Open aidenpearce001 opened 1 year ago

aidenpearce001 commented 1 year ago

It worked few days ago but today i got this error and still not find solution yet : ! [remote rejected] main -> main (shallow update not allowed)

aormsby commented 1 year ago

Please provide more info, or I can't help

GGeorggg commented 1 year ago

Hi,

same for me too: it broke somewhere between 2023-01-27T17:42:29.8455646Z and 2023-02-03T10:26:18.9201843Z

The only difference i can see, is the image:

https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20230122.1 (OK) https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20230129.2 (BROKE)

when Pushing synced data to target branch. is called, i do get:

 ! [remote rejected]         MOODLE_401_STABLE -> MOODLE_401_STABLE (shallow update not allowed)

i already switched v3 to run an unshallow checkout: 

    - name: Checkout target repo
      uses: actions/checkout@v3
      with:
        ref: MOODLE_401_STABLE
        persist-credentials: false
        fetch-depth: 0

however that did not fix the issue

the new docker image could have changed the git Version, as there was a change commited on 11 Jan 2023 15:12:27 -0300

http://changelogs.ubuntu.com/changelogs/pool/main/g/git/git_2.34.1-1ubuntu1.6/changelog

changes tried, that won´t fix the issue:

runs-on: ubuntu-18.04 runs-on: macos-12 runs-on: windows-latest actions/checkout@v1

changes that actually fixed the issue 🤦‍♂️:

shallow_since: 2 month ago

regards Georg

aidenpearce001 commented 1 year ago

Please provide more info, or I can't help

I was forked a repo and it's run find for several day until i have this error !

88092ce9f0edf49152b074cf6c448f4122dac3bf Auto Generated New Template Addition List [Tue Feb 7 06:11:08 UTC 2023] :robot: 11b7a4373b930516ec707354432c3e8de88c1b96 Merge pull request #5479 from Akokonunes/patch-185 249c84fe49b6b3a9c30ce3bef62ddc6d62d4e3a0 metadata-update f4ee6d8b47c3ddd83c80141aad0dbb0969e43c82 Auto Generated New Template Addition List [Tue Feb 7 05:24:23 UTC 2023] :robot: 31c7f01a1bb87aeaa970f2b1d75c3b3522728a6b Merge pull request #6684 from spiarh/update_CVE-2021-38540 469feacec196dd68fea28f5a0839adee487cbd0c Auto Generated New Template Addition List [Tue Feb 7 05:10:26 UTC 2023] :robot: 51684c552d6bcf2f5c013e6cd0c1fdaf7f64ac83 Merge pull request #6673 from projectdiscovery/utility-service-detect 5dba0adbed037b98b3b5ffdc3722d0616e338cc5 updated matcher, removed redirect 8711a7be4d6a9072839a5b57d5d8db5b9151111d Auto Generated New Template Addition List [Tue Feb 7 05:06:54 UTC 2023] :robot: 7d3eff09ea249db614a7180922636009ee103cde Merge pull request #6674 from projectdiscovery/yellowfin-panel 7cdec6141ff1e272c006a2224cf1cfc1508af8dd updated matcher 5f027516cc82e4872bc8a960ff06328451882415 Auto Generated New Template Addition List [Tue Feb 7 04:52:35 UTC 2023] :robot: e812da36fb67c4ab9879c62b1804b5f2545fdb9a Merge pull request #6677 from imhunterand/patch-2 b8e613ff030adfe1b339dae10750123cbce4df07 change from google.com -> evil.com b0cf5306c399f19d9de63ca1e4bc8e9824742c11 Auto Generated CVE annotations [Tue Feb 7 04:35:56 UTC 2023] :robot: 3abd38eaaa6dfb2ea6ebe236269bfb7545c41ec1 updated path b40089ae2d3895ae12183260ea4195b8501e7cd1 updated metadata, name and request 21e2d28d75241cfa31fdd41c9734f29b2c2c01fc Auto Generated New Template Addition List [Tue Feb 7 04:20:02 UTC 2023] :robot: b79e5186f528b2071d9fc8a156ef1c48a7f98a4f Merge pull request #6679 from theamanrawat/CVE-2021-25114 8334d6f96a0b06c63a4efea4d38cb6cd13dba35b Auto Generated New Template Addition List [Tue Feb 7 04:10:00 UTC 2023] :robot: 24401daad950d6caf79c0e88efe589430d312f17 Merge pull request #6682 from projectdiscovery/pussycat0x-patch-2 da02f374cc244ac48caab485abd9df79fd151408 Auto WordPress Plugins Update [Tue Feb 7 04:02:03 UTC 2023] :robot: f0836729ead43edf0bf2bfd9b6db78257eefdb28 fix name , spacing and tag 3576fa515878502b8c887a10c67ad66d9be2cb8b Auto Generated CVE annotations [Tue Feb 7 03:47:36 UTC 2023] :robot: 81d2b87fe97356a4428a82bb540500cbb06519f1 Auto Generated New Template Addition List [Tue Feb 7 03:31:49 UTC 2023] :robot: de403f45524c9dda560e695f0c8b73337642b523 Merge pull request #6625 from MostInterestingBotInTheWorld/dashboard 77890edc346bc118141803dd9ce886d784a96e58 workflow fix 0610e45ecf1f723db61d065614935a06295ffb4a syntax fixes f2e530fa0e7c7344581bbc5f08ca7b89a526daa2 Enhancement: network/detect-jabber-xmpp.yaml by md e3b26e37a5a02f80a3a324d96f56d0f4dbe9f5e2 Enhancement: network/detect-addpac-voip-gateway.yaml by md 55147fb10b0379f2b022841f10cf92d4789d6423 Enhancement: misconfiguration/zabbix-error.yaml by md 4df7fef49509e3d82c5f8fc4325f318794fd1d68 Enhancement: misconfiguration/wp-registration-enabled.yaml by md dec7413c95eaeccd98412861169d1c85c64bdcaa Enhancement: misconfiguration/webdav-enabled.yaml by md a000c3fc9ce5947daf1859e8f1357b0ac9bf2b9a Enhancement: misconfiguration/wamp-xdebug-detect.yaml by md 2c97953b4bbc670d2400a28633563c0db4a9d228 Enhancement: misconfiguration/unauth-selenium-grid-console.yaml by md 0d258cfc98924d4de2d401c569a2fd5fd396eacf Enhancement: misconfiguration/tomcat-scripts.yaml by md 87ef9e88b211287f85eda37692381af3d8b790dc Enhancement: misconfiguration/springboot/springboot-status.yaml by md b636b9c0ef459547ff1806d7073a36f0a29bed7e Enhancement: misconfiguration/springboot/springboot-scheduledtasks.yaml by md e00b1e2dc47d6f0a691c4e08c88ed51485cbf820 Enhancement: misconfiguration/springboot/springboot-loggerconfig.yaml by md 089bf01b776d1941d00bc2c5dd1a2dd8dfe8104c Enhancement: misconfiguration/springboot/springboot-info.yaml by md ee9f71ce21b86ca7729b1d3b4209a47583622f58 Enhancement: misconfiguration/springboot/springboot-auditevents.yaml by md 7a4979c81a65437eb63f830bb225fdb9d6f77d6e Enhancement: misconfiguration/springboot/springboot-health.yaml by md 54d5955b9ea3744b09f68d2d23ddae6b30d3a33d Indentation fix ff7575884b9aecd6d0cd3ed0ea77e90fc5cf96c2 duplicate field fix 6eb1df20f9aaf8198207c3f6a37c3b179fea13f7 lint fix 4979936c942c5529910025527e2766d4d45841e8 lint fix a7e880335981aaf7d06a9e637dd4f2e902d82d39 lint fix 6e5d2b6e14f969952d6e40916657a97064ad39f4 lint fix f7b355aa6127bfba0dd5c2ff129c0b6adb3efa4f lint fix f59812fe8ad83e9bbdc3d99a8bac43cd930d8a8b lint fix 0b5c0d6698ef86355b33040d7030a5d0c59fa8e6 lint fix 68450e07c50a6eb64862744cc37b298511b2bd5d Update and rename webeditors.yaml to webeditors-check-detect.yaml fee8ede5fa6c9ddd8a7d8dd5675342b5d777f8fe Merge branch 'main' into dashboard 4e7bc936d40c8aa90671ae6c0886b7b422c1a6e4 Revert "updated id and template name" 224347c62544847769525483c3c2fb64871307ea updated id and template name c858ed69b41a10736a484056c10c1e06f3a79f9e updated metadata 818b243e3e5ba615a0d14454c6835f688ebe1e38 updated metadata dd8591aaa51cd419676add54d0d6c0506af9d362 updated severity, cvss , name f762917e4a3d103d00958fd1a31604ba9991cc7d updated id, severity,cvss e2eae9d51a079440d0af7ef23856045f9d951356 update cvss f0162dbeb901b0af1b711fb723c6e4b75734896c updated severity & cvss c262ee17deac3bf2264f57def046f1650bc9e3ff updated metadata, template fix 8873800d70a3617bbdd5900a032bbc07d9ad46aa updated metadata b46e257f00062e89246c285370d6997e587ff5bd template fix a27a47a080ba323b1d822d78fc6b27719117c71a lint fix e563b311426e87af2ad7b05bd071e42eb54c4c9a template fix db2fa6dfb259cd3a0ea026fc3dd548475bf67bd4 template fix 69ddb02734a94800ffa6e561ea8dac6c6b2fc2b4 fix: update matcher to match vuln 2.0.x versions for airflow CVE-2021-38540 d47e6ee9e2701e555b5f277ad77a8ff6759d1c5b updated metadata 4787dbd5a7443933fd2e15efd50f0b62e71934fa updated severity and cvss b267038885a0a74691254fea65816d182f98c79e updated id,metadata 0bad23cc86c15960663ba3d61a0be64b650f8c33 updated path, severity and cvss c6021ed88eb106c3ad3f239415aa5effbcf22d7d Update AutoSync.yml 3f2f29a9b5e1481ce29af8441d24a6e4ecf53c1d Enhancement: misconfiguration/springboot/springboot-auditevents.yaml by md f33021c8ee80c8b49a60d801f72df08796fe0536 Enhancement: misconfiguration/server-status.yaml by md 247c5c8550129d7e4e5ee01a671f95e44dcde110 Merge branch 'projectdiscovery:main' into main ... ! [remote rejected] main -> main (shallow update not allowed)

I'm using checkout@v1

uses: actions/checkout@v1 with: fetch-depth: 0 token: ${{ secrets.WORKFLOW_TOKEN }}

aidenpearce001 commented 1 year ago

Hi,

same for me too: it broke somewhere between 2023-01-27T17:42:29.8455646Z and 2023-02-03T10:26:18.9201843Z

The only difference i can see, is the image:

https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20230122.1 (OK) https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20230129.2 (BROKE)

when Pushing synced data to target branch. is called, i do get:

 ! [remote rejected]         MOODLE_401_STABLE -> MOODLE_401_STABLE (shallow update not allowed)

i already switched v3 to run an unshallow checkout:

    - name: Checkout target repo
      uses: actions/checkout@v3
      with:
        ref: MOODLE_401_STABLE
        persist-credentials: false
        fetch-depth: 0

however that did not fix the issue

~the new docker image could have changed the git Version, as there was a change commited on 11 Jan 2023 15:12:27 -0300~

~http://changelogs.ubuntu.com/changelogs/pool/main/g/git/git_2.34.1-1ubuntu1.6/changelog~

changes tried, that won´t fix the issue:

runs-on: ubuntu-18.04 runs-on: macos-12 runs-on: windows-latest actions/checkout@v1

changes that actually fixed the issue 🤦‍♂️:

It was the upstream that was to shallow to reach back in time .. adding to the with environment/argument:

shallow_since: 2 month ago

regards Georg

I Had add shallow_since and it's not work in my case

GGeorggg commented 1 year ago

Hi @aidenpearce001

i think this is due to changes within .github/workflow in upstream, if your ${{secrets.WORKFLOW_TOKEN}} does not have scope workflow, the push might fail.

regards Georg

aidenpearce001 commented 1 year ago

Hi @aidenpearce001

i think this is due to changes within .github/workflow in upstream, if your ${{secrets.WORKFLOW_TOKEN}} does not have scope workflow, the push might fail.

regards Georg

The WORKFLOW_TOKEN is my personal Token and i also tick in the Workflow Option

rmarqques commented 1 year ago

The same for me, I am using V3.4, and today (30 March 2023) I started to receive this error. I switched back to V3.0 and it worked to me.