Delete FUNDING.yml #244
Merged
Delete FUNDING.yml #244
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
|
Funding per client is allowed. Thanks 👍 |
|
We've decided that we should not stick out since we're the only client doing this. 👍 |
jimdogx
approved these changes
Apr 2, 2025
|
This has only ever come up a couple times, but yes the policy is that anything in the org should use the org funding configuration. (Just commenting for future reference.) |
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.
It used to be policy that official clients used the organizations default funding file but maybe there has been a policy change?
This PR updates the repo to match the other jellyfin repos.