docs update to avoid shallow update not allowed
#1303
Conversation
When I followed the instructions, I received the following error: ``` > Pushing pull request branch to 'origin/bundle-update-1667232038' /usr/bin/git push --force-with-lease origin HEAD:refs/heads/bundle-update-1667232038 To github.com:****/****.git ! [remote rejected] HEAD -> bundle-update-1667232038 (shallow update not allowed) error: failed to push some refs to 'github.com:****/****.git' ``` this setting `fetch-depth: 0` in the checkout action resolved the issue.
|
Please could you show me the workflow where this occurred? I want to understand the conditions that made this necessary. There are definitely cases where this isn't necessary. For example, this test case. |
|
Maybe the difference is in the test case, you're pushing a new file and in my example, I'm updating an existing file? |
|
Thank you for the workflow.
It's actually an update, not a new file. You can see the file checked in here. I'm very confused about why this is happening in your workflow. Normally, this error only occurs if you are pushing to a new repository. When pushing to a branch in the same repository it should not occur I think. |
|
strange. Will try again without (side note: it's delightful to have feedback on an issue or PR soon after opening it. thank you!) |
|
well... unsurprisingly it worked. Sorry to waste your time! I wonder where the original error came from 🤷♀️ |
|
No worries 😄 If you figure it out please let me know because it might be a strange edge case that I can document. |
When I followed the instructions, I received the following error:
this setting
fetch-depth: 0in the checkout action, which does an unshallow clone, resolved the issue.