-
Notifications
You must be signed in to change notification settings - Fork 380
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
fix: handling of branch names with slashes #131
Conversation
Thanks for the changes! Could you please run the following command locally to ensure all pre-commit install After that, amend your last commit to trigger the hooks: git commit --amend --no-edit Finally, push the changes with: git push --force-with-lease This ensures that all necessary checks and formatting are applied. Let me know if you run into any issues! 😊 |
e413b33
to
61da031
Compare
Thanks for the comments @filipchristiansen, changes have been incorporated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thank you @gowthamkishore3799!
@cyclotruc, can you have a check, and if you think it looks good, you can go ahead and merge.
This update addresses issues related to the handling of branch names containing slashes:
feature/fix1
without errors.