85
Introducing LemmyApps.com - Easily discover Lemmy apps that best suit your needs
(www.lemmyapps.com)
A home for discussion of Lemmy apps and tools for all platforms.
RULES:
An extensive list of Lemmy apps is available here:
Visit our partner Communities!
Lemmy Plugins and Userscripts is a great place to enhance the Lemmy browsing experience. !plugins@sh.itjust.works
Lemmy Integrations is a community about all integrations with the lemmy API. Bots, Scripts, New Apps, etc. !lemmy_integrations@lemmy.dbzer0.com
Lemmy Bots and Tools is a place to discuss and show off bots, tools, front ends, etc. you’re making that relate to lemmy. !lemmy_dev@programming.dev
Lemmy App Development is a place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform. !lemmydev@lemm.ee
Thank you for pointing this out! LemmyApps uses the "PushedAt" field from the GitHub repository response to determine the latest commit. However, this appears to be the latest commit across all branches, including
dependabot/*
branches.I may have found a workaround that considers just the main branch. I will add this to the priority implementation list.
If you end up only considering a single branch, it would be a good idea to let app owners change which branch is considered “main”. Many apps have a main branch that stores the live code state, and a second development branch where all of the work is done. When an update is released, code is pushed from the development branch to the main branch. In this setup, it would make the most sense to show the most recent commit on the development branch rather than the main branch.