-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Could possibly commit a large amount then push? #1
Comments
I could add that functionality if you'd like. The reason I decided to push after every commit day was so that you could see the changes on your calendar immediately, so you would have a visual track of the progress of the script |
I've found it to work much much faster when it doesn't immediately push after each individual commit. Took me around 45 minutes instead of 8 hours. |
you could print progress information to the python console instead |
#12 resolves this. |
Thank you @benhutchins c: 👍 |
@robobenklein #21 Does exactly what you are describing. |
I'm thinking that if you were to simply change the flow so that it commits a hundred or so times before it actually pushes, it could operate at a much faster rate (and not depend so much on having a good internet connection.)
The text was updated successfully, but these errors were encountered: