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

Remove footgun with add.branch_replacements #92

Merged
merged 1 commit into from
Oct 22, 2024
Merged

Remove footgun with add.branch_replacements #92

merged 1 commit into from
Oct 22, 2024

Conversation

9999years
Copy link
Owner

If you defined add.branch_replacements in your config.toml, but the result of applying the replacements included a /, git-prole would naively use that as the basename of a directory, causing problems (like the parent directory not existing).

Now, the last component of the result is used, to match the behavior when add.branch_replacements is not set.

Fixes #91

If you defined `add.branch_replacements` in your `config.toml`, but the
result of applying the replacements included a `/`, `git-prole` would
naively use that as the basename of a directory, causing problems (like
the parent directory not existing).

Now, the last component of the result is used, to match the behavior
when `add.branch_replacements` is not set.
@9999years 9999years enabled auto-merge (squash) October 22, 2024 20:28
@9999years 9999years merged commit f649fbf into main Oct 22, 2024
4 checks passed
@9999years 9999years deleted the fix-91 branch October 22, 2024 20:29
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Branch replacement regexes can make invalid directory names
1 participant