mirror of
https://github.com/beetbox/beets.git
synced 2025-12-06 08:39:17 +01:00
Add beets-filetote to community plugins docs (#5779)
Add link to community plugin [`beets-filetote`](https://github.com/gtronset/beets-filetote). This plugin is the spiritual successor to [beets-copyartifacts](https://github.com/adammillerio/beets-copyartifacts) (`beets-copyartifacts3` was last updated 3 years ago) and [beets-extrafiles](https://github.com/Holzhaus/beets-extrafiles) (last updated 5 years ago). Given the updates and changes in beets and how outdated those plugins are, does it make sense to keep `beets-copyartifacts` in the community plugins list? --------- Co-authored-by: Sebastian Mohr <39738318+semohr@users.noreply.github.com>
This commit is contained in:
parent
589bd6d599
commit
b92a1b3d98
1 changed files with 5 additions and 0 deletions
|
|
@ -465,6 +465,10 @@ Here are a few of the plugins written by the beets community:
|
|||
`dsedivec`_
|
||||
Has two plugins: ``edit`` and ``moveall``.
|
||||
|
||||
`beets-filetote`_
|
||||
Helps bring non-music extra files, attachments, and artifacts during
|
||||
imports and CLI file manipulation actions (`beet move`, etc.).
|
||||
|
||||
`beets-follow`_
|
||||
Lets you check for new albums from artists you like.
|
||||
|
||||
|
|
@ -560,6 +564,7 @@ Here are a few of the plugins written by the beets community:
|
|||
.. _cmus: http://cmus.sourceforge.net/
|
||||
.. _beet-amazon: https://github.com/jmwatte/beet-amazon
|
||||
.. _beets-alternatives: https://github.com/geigerzaehler/beets-alternatives
|
||||
.. _beets-filetote: https://github.com/gtronset/beets-filetote
|
||||
.. _beets-follow: https://github.com/nolsto/beets-follow
|
||||
.. _beets-ibroadcast: https://github.com/ctrueden/beets-ibroadcast
|
||||
.. _iBroadcast: https://ibroadcast.com/
|
||||
|
|
|
|||
Loading…
Reference in a new issue