How should monorepo-based implementations be submitted? (Clarifying the “dedicated GitHub repository” requirement)

[yamcodes]

Hi, first of all, thank you for the RealWorld project. It’s been a great reference, and I really appreciate the work that’s gone into it.

So far, I’ve contributed three RealWorld implementations:

• Bepstack
• Bedstack
• encore-realworld

Recently, I needed to update the links for Bepstack and Bedstack after moving ownership from an organization account to my personal GitHub account. To do that, I removed and re-submitted the entries.

Both submissions were rejected with the same note:

Your implementation should be in a dedicated GitHub repository.

I’d love some clarification on what “dedicated repository” means in this context.

In our case, the RealWorld implementations (especially Bedstack) live inside a monorepo. The RealWorld app is a fully working implementation, but it exists as one app or example within a larger stack repository, rather than being the only thing in the repo.

Is this setup acceptable, and if so, what’s the preferred way to submit it?
For example:

• Is pointing directly to the specific app or folder within the monorepo enough?
• Or is the expectation that the repository contains only the RealWorld implementation? (This is challenging for us)

Thanks a lot for the clarification, and again, thank you for maintaining such a valuable project.

Yam

[mvila]

Hi @yamcodes,

I'm sorry, but we expect the GitHub repository to contain only the RealWorld implementation. I hope you can find a solution.

[yamcodes]

Thanks for the response, @mvila. I'll try to think of something...

May I kindly ask what is the reason for this expectation? After all, monorepos are a popular way of keeping related code together.

[mvila]

We consider a RealWorld implementation to be a project in its own right, with its own lifecycle. For example, it has its own dedicated issues, the maintainer can change over time, etc.

Moreover, some CodebaseShow features, such as "Mark as unmaintained" or "Claim ownership", cannot work without this requirement.

[c4ffein]

Thanks for the contribution @yamcodes
We link implementations to standalone repos, but you can work around this limitation:

For example, https://github.com/splitsh/lite or a regular git subtree split can auto-publish the relevant subdirectory to a dedicated repo via CI.
The split repo is just a read-only mirror that stays in sync with your monorepo. Symfony and others use this pattern.

Happy to help if anything is still blocking.