Skip to content

mcp: support SEMCODE_GIT_REPO environment variable#33

Open
groeck wants to merge 1 commit intofacebookexperimental:mainfrom
groeck:local
Open

mcp: support SEMCODE_GIT_REPO environment variable#33
groeck wants to merge 1 commit intofacebookexperimental:mainfrom
groeck:local

Conversation

@groeck
Copy link
Copy Markdown

@groeck groeck commented Apr 15, 2026

Add SEMCODE_GIT_REPO environment variable support for specifying the git repository path in semcode-mcp and semcode. This allows the MCP host process to provide the repository location via the environment when command line arguments cannot be easily modified.

The priority order is:

  1. --git-repo command line argument
  2. SEMCODE_GIT_REPO environment variable
  3. Current directory (default)

Enable the env feature for clap in Cargo.toml to support the env attribute in the Args struct.

Add test code to verify that the environment variable is correctly supported and respects the priority order.

Add SEMCODE_GIT_REPO environment variable support for specifying the git
repository path in semcode-mcp and semcode. This allows the MCP host
process to provide the repository location via the environment when
command line arguments cannot be easily modified.

The priority order is:
1. --git-repo command line argument
2. SEMCODE_GIT_REPO environment variable
3. Current directory (default)

Enable the env feature for clap in Cargo.toml to support the env
attribute in the Args struct.

Add test code to verify that the environment variable is correctly
supported and respects the priority order.

Signed-off-by: Guenter Roeck <linux@roeck-us.net>
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented Apr 15, 2026

Hi @groeck!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented Apr 15, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Meta Open Source bot. label Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Meta Open Source bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant