googleapis / googleapis/librarian
python: remove post-processor staging
Open
priority: p3
- Dominant language
- Go
- Stars
- 45
- Forks
- 61
- Avg merge
- 19h 11m
- Merged PRs (30d)
- 181
Description
We shouldn't have to generate to an owl-bot-staging directory at all. Once we've removed the use of synthtool, we can generate directly into the right place. We then shouldn't have anything to clean up afterwards (and ideally we don't even need to figure out the repo root.)
Contributor guide
Research direction
Start by locating the Python generation path and tracing its uses of synthtool, owl-bot-staging, cleanup, and repository-root detection. Done means generation writes directly to the intended location without staging or post-generation cleanup; the issue does not name specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100