-
-
Notifications
You must be signed in to change notification settings - Fork 505
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
Add new LXC: NextPVR #391
Add new LXC: NextPVR #391
Conversation
Co-authored-by: Håvard Gjøby Thom <[email protected]>
Co-authored-by: Håvard Gjøby Thom <[email protected]>
@havardthom Done & Tested | Approve pending |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are strings in all other json's. Perhaps they should be numbers, but then it should be fixed everywhere
Co-authored-by: Håvard Gjøby Thom <[email protected]>
Co-authored-by: Håvard Gjøby Thom <[email protected]>
Co-authored-by: Håvard Gjøby Thom <[email protected]>
I was wondering, because it doesn't actually need “[INT]” if it's just numbers? But okay, it's adjusted ^^ |
Description
Add new LXC: NextPVR.
I only can test the usage of the ui. i dont have an System for it.
After Merge we can add the requester as final reviewer / or need later an bugfix.
Fixes # (issue)
Fixes #384
Type of change
Prerequisites
The following efforts must be made for the PR to be considered. Please check when completed: