You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I created a workflow which pushes updated visual regression screenshots when those tests fail, pushing the images takes twice as long as running the entire presubmit lint/test suite.
Expected behavior
Based on pushing from my computer and pushing that happens during other Actions (like semantic release) I expect it to be quite fast to push a single commit to git.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Same here in a private repo. I am pushing to a lightweight branch in a repo that has a lot of heavy branches. It feels as if the command pulls all branches first before pushing. Just judging by its time – it takes 6+ minutes.
UPD I removed the pull option but the action did not become faster. It was originally pull: "--rebase --autostash". There must be a way of pulling just a single branch, but performance is not a high priority in my case. It’d be great if the action was as fast as running git commit & git push though.
Hi @kachkaev, thanks for writing in
Would you be able to provide some logs? I'm trying to replicate this behavior since I should have some time to look into it, but the logs from the issue author have expired.
Total task duration was 6:26 in this case. As you can see from the logs, the problem is likely to do with syncing all branches, not just one. I have a rather ‘wide’ repo, i.e. 100+ branches with unrelated stuff in them. Syncing everything is what probably takes a while.
Thanks for the logs! Yeah, it's definitely the fetch that's slowing down the action: I was able to reproduce this on a fork of the repo the author was having problems too.
I think I'll add an option to disable fetching so that large repos can use the action too. Disabling the fetch step will impact branch and tag creation, so I'll make sure to add some documentation in the README
Activity
stale commentedon Apr 23, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
kachkaev commentedon Aug 11, 2022
Same here in a private repo. I am pushing to a lightweight branch in a repo that has a lot of heavy branches. It feels as if the command pulls all branches first before pushing. Just judging by its time – it takes 6+ minutes.
UPD I removed the
pulloption but the action did not become faster. It was originallypull: "--rebase --autostash". There must be a way of pulling just a single branch, but performance is not a high priority in my case. It’d be great if the action was as fast as runninggit commit&git pushthough.EndBug commentedon Aug 18, 2022
Hi @kachkaev, thanks for writing in
Would you be able to provide some logs? I'm trying to replicate this behavior since I should have some time to look into it, but the logs from the issue author have expired.
kachkaev commentedon Aug 18, 2022
👋 @EndBug! Here are my logs:
Total task duration was 6:26 in this case. As you can see from the logs, the problem is likely to do with syncing all branches, not just one. I have a rather ‘wide’ repo, i.e. 100+ branches with unrelated stuff in them. Syncing everything is what probably takes a while.
In the meantime, I’ve temporarily switched to:
Hope this info helps! 🙌
EndBug commentedon Aug 20, 2022
Thanks for the logs! Yeah, it's definitely the fetch that's slowing down the action: I was able to reproduce this on a fork of the repo the author was having problems too.
I think I'll add an option to disable fetching so that large repos can use the action too. Disabling the fetch step will impact branch and tag creation, so I'll make sure to add some documentation in the README
feat: add `fetch` input
EndBug commentedon Aug 22, 2022
Alright, I've opened a PR (#423) with a new input that would let you customize or skip the
git fetchcommand.@kachkaev could you review it?
kachkaev commentedon Aug 22, 2022
Great, thank @EndBug! The diff makes sense 👍
feat: add `fetch` input (#423)
EndBug commentedon Aug 22, 2022
@all-contributors please add @melink14 and @kachkaev for their bug report
allcontributors commentedon Aug 22, 2022
@EndBug
I've put up a pull request to add @melink14! 🎉
EndBug commentedon Aug 22, 2022
@all-contributors please add @kachkaev for their bug report
allcontributors commentedon Aug 22, 2022
@EndBug
I've put up a pull request to add @kachkaev! 🎉
EndBug commentedon Aug 22, 2022
Alright, I've just published the feature in
v9.1.0(alsov9andlatest)Thanks everyone 🎉
ci(presubmit): Fixes several quality of life issues in presubmit work…
ci(presubmit): Fixes several quality of life issues in presubmit work…