Skip to content

Conversation

MaxKless
Copy link

@MaxKless MaxKless commented Sep 29, 2025

Motivation and Context

Discussion from this issue: #538
We want to make it clearer that repo name & server name do not HAVE to be the same, especially in monorepos.

@tadasant this seems like a minor thing that doesn't have to be documented specifically, lmk if you disagree :)

How Has This Been Tested?

Tested the init flow locally, running the built init command from a subfolder and the repo root.

Breaking Changes

No

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

domdomegg
domdomegg previously approved these changes Oct 3, 2025
@domdomegg
Copy link
Member

Thanks! Are you able to fix the merge conflicts and we can get this shipped 🚀

@MaxKless
Copy link
Author

MaxKless commented Oct 6, 2025

awesome, glad to hear it @domdomegg! I rebased and fixed the merge conflicts :)

Copy link
Member

@rdimitrov rdimitrov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Left a small comment 👍

// If we're in a subdirectory, use the current folder name
if subfolder != "" {
if cwd, err := os.Getwd(); err == nil {
folderName := filepath.Base(cwd)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems we use subfolder as a boolean even though it's a string. Wouldn't it be better to reuse the subfolder variable we already have?

For example if it's != "" construct the path using it (and avoid reading the base path again), otherwise proceed as if we are in the root repo.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you're completely right, I pushed a fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants