Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Separate smee-client and smee-server into separate repositories

See original GitHub issue

I’d like to chat about moving smee-client and the actual server into two separate repositories. My main motivation to do that is to ease contributions (contributing to the two is confusing, including for me) make build times faster (CI will have to test half the code).

What do y’all think? Is this something worth the small amount of effort, or is it less confusing the way it is now?

cc @tcbyrd

Issue Analytics

State:
Created 5 years ago
Comments:13 (12 by maintainers)

Top GitHub Comments

1reaction

JasonEtcocommented, Dec 17, 2018

We should setup probably setup some automation to ensure they’re tested against each other

Yeah, good call. Zero code is shared between the client and server, so it might be tricky to do - but interestingly we don’t already have any tests that work integrate both; so we’re not losing anything in the move, though it may be more difficult.

Sounds like three 👍s! Thanks all for your quick response 😊 Now, how do we feel about these names for the two repos?

smee-client
smee-server

We can hold on to smee and archive it, with links to those two in the README. Thoughts?

0reactions

wolfy1339commented, Mar 19, 2019

Not stale.

From: stale[bot] notifications@github.com Sent: Tuesday, March 19, 2019 5:19:36 PM To: probot/smee Cc: wolfy1339; Manual Subject: Re: [probot/smee] Separate smee-client and smee-server into separate repositories (#87)

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/probot/smee/issues/87#issuecomment-474588879, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEYfFVbeG0WzVmImQZpgswlIcSeF3S8kks5vYVRogaJpZM4ZU8_l.

Top Results From Across the Web

Keep project parts in one repository or split into multiple

I would suggest each part should have its own repo. The reasons are client and server have very different release cycle.

Github integration with SMEE client: Jenkins doesn't like ...

So connectivity from Jenkins to SMEE server, SMEE server to SMEE client and SMEE client to Jenkins all seem to be working. What...

Mono- or Multi-Repository: A Dilemma in the Serverless World

Multi-repo allows you to separate teams' areas of responsibility. Since each service resides in its repository, multi-repo often helps you avoid the ...

Split a repository in two | Bitbucket Cloud - Atlassian Support

Learn how to move a directory from one repository into another and retain the history in Bitbucket ... A code repository typically has...

smee-client - npm Package Health Analysis - Snyk

Based on project statistics from the GitHub repository for the npm package smee-client, we found that it has been starred 274 times, and...