Skip to content
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

Update path include/exclude spec and behavior #37

Merged
merged 2 commits into from
Jul 30, 2024

Conversation

drdavella
Copy link
Member

No description provided.

@drdavella drdavella requested review from nahsra and gilday July 30, 2024 16:18
cli.md Outdated Show resolved Hide resolved
Co-authored-by: Johnathan Gilday <[email protected]>
@@ -41,16 +41,9 @@ The `executable` could involve multiple command line tokens (e.g., `npm run` or
- The only required field is `<project directory>`. However, this field is not required if running either `--help`, `--list`, `--describe`, or `--version`.
- You cannot legally specify any argument more than one time.
- If `--output` is given, it indicates the path where a codetf or diff file will be created (depending on the value of `--output-format`). Otherwise no output file is generated.
- All codemod rules are loaded by default unless `--codemode-include` specifies a list. `-codemode-exclude` works off all default codemods.
Copy link
Contributor

Choose a reason for hiding this comment

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

We need a linter rule in every repository for "codemode" 😂

@drdavella drdavella merged commit ce7ada1 into main Jul 30, 2024
2 checks passed
@drdavella drdavella deleted the path-includes-excludes branch July 30, 2024 18:32
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.

2 participants