Sirherobrine23/Jellyfin_Xtream
1
0
Fork 0
Code Issues 26 Pull Requests 6 Actions Releases Wiki Activity

Ability to default numbering to 1-1xxx #76

New Issue
Open
opened 2023-09-28 16:16:51 +00:00 by jmvbrown · 0 comments
jmvbrown commented 2023-09-28 16:16:51 +00:00 (Migrated from github.com)
Copy Link

Is it possible to add option to default the numbering of channels so they are grouped together. For example, Group 1 is channels 1-20, Group 2 is channels 21-40, Group 3 is channels 41-60 and so on instead of every group starting with 1. For whatever reason, the override option never works for me.

Is it possible to add option to default the numbering of channels so they are grouped together. For example, Group 1 is channels 1-20, Group 2 is channels 21-40, Group 3 is channels 41-60 and so on instead of every group starting with 1. For whatever reason, the override option never works for me.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked
This PR is blocked due to a commented reason
 breaking
This PR introduces breaking changes
 bug
This PR or Issue describes or fixes something that isn't working
 chore
This PR contains repository maintenance changes
 ci
This PR updates or changes something CI related
 confirmed
This Issue describes a bug that has been confirmed by a org member
 dependencies
This PR updates or changes a dependency file
 deprecated
This PR marks a feature, function or other public API element as deprecated
 documentation
This PR or Issue aims to improve or add to documentation
 duplicate
This Issue or PR is a duplicate of an existing Issue or PR
 feature
This PR or Issue requests or introduces a new feature
 github-actions
This PR updates or changes GH Actions used in this repo
 good first issue
This Issue contains a requirement easy to be picked up by project newcomers
 help wanted
This Issue or PR requires extra attention and/or requires external help
 invalid
This Issue describes an invalid request or bug report
 major-bug
This PR fixes a major bug
 major-feature
This PR introduces a major new feature
 nuget
This PR updates or changes some NuGet dependencies
 question
This Issue contains a question
 release-prep
This PR is a meta PR to prepare for the next release
 removed
This PR removes a feature, function or other public API element
 reverted
This PR reverts a commit or multiple commits
 skip-changelog
This PR gets ignored by the Release Drafter workflow
 tests
This PR adds or imposes tests (e.g. coverage, quality, ...)
 wontfix
This Issue contains a request or 'bug' that wont be fixed (e.g. out-of-scope, not-an-issue, ...)
No Label feature
Milestone
No items
No Milestone
Assignees
Clear assignees
Sirherobrine23
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Sirherobrine23/Jellyfin_Xtream#76
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?