DDEV addons - archived and forked repositories #6643
Replies: 2 comments 6 replies
-
I think retaining the ability to install/remove archive add-on is important.
Forks do NOT appear in the lists. If they did, you would see a ton of addons from @GuySartorelli as they raining down document update PRs at the moment. (Thank you!) |
Beta Was this translation helpful? Give feedback.
-
@GuySartorelli Thank you very much for all these updates!
We can exclude archived from the list with https://api.github.com/search/repositories?q=topic:ddev-get+fork:true+archived:true |
Beta Was this translation helpful? Give feedback.
-
Right now, an addon in a repository which has been archived doesn't indicate that it's abandoned.
There are two options I can think of for this:
ddev add-on list --all
list at all, but still allow it to be installed. Then, on installation, output some "this add-on is in an archived repository" message.ddev add-on list --all
. As above, add a message on installation.The other scenario I thought of after I noticed this is forked repositories. I haven't checked this, but presumably forks display in the addon list? If they do... should they? If they don't, then I assume this has already been discussed and thought about.
Beta Was this translation helpful? Give feedback.
All reactions