You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Codegen parses your entire codebase into a graph representation
58
+
2. The codemod function is executed against this graph
59
+
3. Any changes made by the codemod are tracked
60
+
4. Changes are automatically applied to your local files
61
+
5. A summary of changes is displayed
67
62
68
63
<Note>
69
-
Your working directory must be clean (no uncommitted changes) when using `--apply-local`. If you have uncommitted changes, the command will provide instructions for resolving the situation.
64
+
The codebase parsing step may take a few moments for larger codebases. Learn more in [How it Works](/introduction/how-it-works.mdx)
70
65
</Note>
71
-
72
-
## Common Issues
73
-
74
-
### Uncommitted Changes
75
-
If `--apply-local` fails due to uncommitted changes, you have two options:
76
-
77
-
1. Save your changes:
78
-
```bash
79
-
git status # Check working directory
80
-
git add .# Stage changes
81
-
git commit -m 'msg'# Commit changes
82
-
codegen run ... # Run command again
83
-
```
84
-
85
-
2. Discard changes (⚠️ destructive):
86
-
```bash
87
-
git reset --hard HEAD # Discard uncommitted changes
88
-
git clean -fd # Remove untracked files
89
-
codegen run ... # Run command again
90
-
```
91
-
92
-
### Multiple Codemods
93
-
If multiple codemods share the same name, specify the exact file path:
94
-
```bash
95
-
codegen run ./path/to/specific/codemod.py
96
-
```
97
-
98
-
## Next Steps
99
-
100
-
After running a codemod:
101
-
1. Review the changes in the web UI or diff preview
0 commit comments