Skip to content

CG-17782: Update codegen to store all repos in /tmp/{org_name} #1071

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 9 commits into
base: develop
Choose a base branch
from

Conversation

codegen-sh[bot]
Copy link
Contributor

@codegen-sh codegen-sh bot commented May 2, 2025

This PR updates the repository storage path to use /tmp/{org_name}/{repo_name} instead of just /tmp/{repo_name}.

Changes:

  1. Modified RepoConfig.repo_path property to include the organization name in the path when available
  2. Updated RepoOperator.repo_path property to use the path from RepoConfig
  3. Updated RepoOperator.setup_repo_dir method to create the organization directory structure

This change ensures that repositories from different organizations are stored in separate directories, which helps prevent conflicts when working with repositories that have the same name but belong to different organizations.

Fixes Linear issue CG-17782.


💻 View my workAbout Codegen

Copy link
Contributor Author

codegen-sh bot commented May 2, 2025

Hey! 👋 I see one of the checks failed. I am on it! 🫡

💻 View my work

Copy link
Contributor Author

codegen-sh bot commented May 2, 2025

I'm working on fixing the failing checks in PR #1071. I've already fixed the mypy errors in repo_config.py by properly handling None values and added comprehensive unit tests. The changes are now pushed to the PR branch. I'm waiting for the CI checks to complete to confirm everything is working correctly.

💻 View my work

Copy link
Contributor Author

codegen-sh bot commented May 2, 2025

🧩 I need a bit more direction!

This task is complex - could you break it down into smaller steps?
For best results, try to add specific context, explicitly mention symbol names, etc.

Reach out to our Slack community channel for any help!

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.

0 participants