Monorepo support for GitHub (release / tag) badges

Currently, it kinda work, but only if it is synced-based lerna monorepo. The thing is that I think we can support independent-versioned monorepo badges too.

For example, you have monorepo that has few packages that are with different versions, and so you have release/tags for each package and here “latest release” isn’t the right fit.

The endpoint probably can be

• /release/:org/:repo/<packageName>
• /release/:org/:repo/<packageName>/v1.2.3
• /release/:org/:repo/<packageName>/latest
• /release/:org/:repo/<packageName>/canary
• /release/:org/:repo/<packageName>/next

It also should support other than packages/ folder. That’s the common case, but there are cases where you must have more workspaces, and you can’t put it to packages/ (some doing it, but there are limitations to this). Or we can support /release/:org/:repo/<packagesDir>/<packageName> too, e.g. /release/tunnckoCore/monorepo/@tunnckoCore/git-semver-tags - @tunnckoCore is a directory in the monorepo, same as packages one.

Something like /release/remarkjs/remark/remark-parse for https://github.com/remarkjs/remark/releases/tag/remark-parse@6.0.3

Or in my case it would be /release/tunnckoCore/monorepo/parse-commit-message.

[tunnckoCore]

Noooope, don’t touch it 🏓 😆

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.