You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see, pull requests often come in pairs: one to dockerfiles and one to whatever-starter-kit. It should be one atomic change. Furthermore, it's inconvenient for contributors to propose new platforms without you creating a new empty starter kit repo first.
Consider merging all this stuff into a monorepo.
It will make getting started a bit harder (one can't just clone favorite-language-starter-kit, has to copy a sub-directory), but I think it's worth it.
The text was updated successfully, but these errors were encountered:
It makes sense, but our current process more closely resembles actual contest situation: separate repository that contains team solution, separate repository that contains Dockerfiles. We have an internal CI that continuosly checks all starterkits against current Dockerfiles, so I can make sure everything works.
Your suggestion is valid though. I'll give it a thought.
As you can see, pull requests often come in pairs: one to dockerfiles and one to whatever-starter-kit. It should be one atomic change. Furthermore, it's inconvenient for contributors to propose new platforms without you creating a new empty starter kit repo first.
Consider merging all this stuff into a monorepo.
It will make getting started a bit harder (one can't just clone favorite-language-starter-kit, has to copy a sub-directory), but I think it's worth it.
The text was updated successfully, but these errors were encountered: