-
-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pushing is slower than expected (> 2min) #386
Comments
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 |
Hi @kachkaev, thanks for writing in |
👋 @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: - name: Commit and push
run: |
git add --all \
&& git commit --message "Update seed data" \
&& git push \
|| true
env:
GIT_AUTHOR_EMAIL: github.actions@my-project.example.org
GIT_AUTHOR_NAME: GitHub Actions
GIT_COMMITTER_EMAIL: github.actions@my-project.example.org
GIT_COMMITTER_NAME: GitHub Actions
working-directory: some-cwd Hope this info helps! 🙌 |
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 |
Great, thank @EndBug! The diff makes sense 👍 |
@all-contributors please add @melink14 and @kachkaev for their bug report |
I've put up a pull request to add @melink14! 🎉 |
@all-contributors please add @kachkaev for their bug report |
I've put up a pull request to add @kachkaev! 🎉 |
Alright, I've just published the feature in |
…flow - Migrates to new `set-output` syntax to avoid deprecation warning. - Marks `fetch: false` when adding commits for significant speed up. - Excludes /screenshots directory when commiting lint fixes. This avoid inadvertantly committing failed screenshot metadata when visual regression tests fail. (Requiring a manual revert) See https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ See EndBug/add-and-commit#386
…flow (#1306) - Migrates to new `set-output` syntax to avoid deprecation warning. - Marks `fetch: false` when adding commits for significant speed up. - Excludes /screenshots directory when commiting lint fixes. This avoid inadvertantly committing failed screenshot metadata when visual regression tests fail. (Requiring a manual revert) See https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ See EndBug/add-and-commit#386
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.
Workflow used
https://github.com/melink14/rikaikun/blob/23fc0df1f33bd32456a73e09ddc16e19c52a3087/.github/workflows/presubmit.yml
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.
Logs
https://github.com/melink14/rikaikun/runs/5803997253?check_suite_focus=true
The text was updated successfully, but these errors were encountered: