Fix upstream url #232
Closed
Fix upstream url #232
Conversation
This file contains 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
…specified in the /etc/plexupdate.cron.conf file.
Add a method to send a slack message and call it if a webhook url is …
… url is specified in the /etc/plexupdate.cron.conf file." This reverts commit 2a0ea34.
|
There's a lot of extra commits due to my mistakes. If you want I can scrap this and start a new fork completely. |
|
Have you seen this actually happen? And don't worry about having too many commits, that's what squash and merge is for. It'll take all of the commits and condense them down to a single commit when it gets merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To Fix #231. Move the upstream URL from the plexupdate-core to the plexupdate.sh script as it needs config variables which are not sources in plex update-core