Updates for Oauth2 support via Yagmail #56
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndyHegemann
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I figured I would open this PR just incase anyone else ran into this annoyance with new google accounts.
While setting up this script, I made a new google account to send the notification emails from, but it turns out that new google accounts no longer let you enable "Less secure app access".
So I added configurable options to use yagmail and oauth2, which only requires the yagmail dependency if enabled.
I also wanted the log file emailed to me if there was an error, so that got added as well.
And, inline with #41 I added a check to abort if there are too many modified/updated files.