Skip to content
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

Support for Plex Movie Scanner #82

Closed
wants to merge 1 commit into from
Closed

Conversation

wampa1
Copy link

@wampa1 wampa1 commented Nov 26, 2020

I think I figured out how to do a pull request. Forked it, then made the change then submit the request I guess.

This uses name and year matching to attempt to mitigate the plex movie scanner guid misalignment with Trakt's available lookups.

Hope this helps. It definitely helped me (and worked like a champ).

Eric

@glensc
Copy link
Collaborator

glensc commented Nov 27, 2020

@wampa1 in the future, create a branch when submitting PR. you may want your master to live it's own life, but it's directly linked to specific PR. any commits you add to branch linked to the PR, will add more commits to the PR. in other words, never create pull request from master branch.

else:
logging.error('Movie [{} ({})]: Unrecognized GUID {}'.format(
movie.title, movie.year, movie.guid))
continue
raise NotImplementedError()
# search and sync movie
try:
search = trakt.sync.search_by_id(x, id_type=provider)
search = []
if ( provider == 'plex' ):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if ( provider == 'plex' ):
if provider == 'plex':

superfluous parens can be dropped

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it's cool with you, I'd like to follow both of your suggestions.

I'll remove the parens (I am 99.99% a Java guy), kill this PR, and start a new one that's from a non-master branch.

I hope killing the PR and starting a new one doesn't cause you any additional concern.

Thanks again!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can force push to the same branch you created the pr, and PR will update. no need to create new PR.

you can also apply the suggestion from web. there's UI for that. but you want then probably git squash the commit locally (and the force push).

@wampa1 wampa1 closed this Nov 27, 2020
Repository owner locked as resolved and limited conversation to collaborators Jan 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants