-
Notifications
You must be signed in to change notification settings - Fork 19
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
Hotfix v0.16.3 #1490
Hotfix v0.16.3 #1490
Conversation
Hey @adelmemariani I have to be annoying about the branch again. This is not a HotFix as it doesn't merge directly into the master branch and also introduces new features. I think you wanted to use the HotFix branch because you think it's easier for you because you only have to create one branch :D If that's the case and you're having trouble creating multiple branches, then you can also create a normal feature branch and reference any issues you implement. HotFix branches only serve a specific use case. If it's not too much trouble, please rename the branch and create a new PR :) Thank you! i suggest a branch name like |
You can use Git to rename the branch, but GitHub will require you to create a new PullRequest because it can't recognize what the previous branch name was. |
|
Thanks alot @adelmemariani. I will close this PR |
Summary of the discussion
Describe the findings of the discussion in the issue or meeting.
Type of change (CHANGELOG.md)
Added
Updated
Removed
Workflow checklist
Automation
Closes #1488
Closes #1489
Closes #1487
Part of #1478
PR-Assignee
Reviewer