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
Would be nice to have the opportunity to configure a unique message for a batch of files.
Concrete example:
In the exampel below, I introduced a new enum and started using it inside 4 existing files. Then I would like to have a single message in a single commit that is simply "refactor: added SvgElementType constants"
So instead of:
│
◇ 4 staged files:
src/features/Picture/screens/CanvasEdit/SvgCanvasDrawMode.js
src/features/Picture/screens/CanvasEdit/SvgViewer.js
src/features/Picture/screens/CanvasEdit/__tests__/SvgViewer.test.js
src/features/Picture/screens/CanvasEdit/constants.js
│
◇ 📝 Commit message generated
│
└ Commit message:
——————————————————
feat(SvgCanvasDrawMode.js): add SvgElementType constant to newElement object
feat(SvgViewer.js): add support for SvgElementType constants in ELEMENT_VIEWERS map
test(SvgViewer.test.js): add tests for SvgElementType constants
feat(constants.js): add SvgElementType constants for SVG elements
——————————————————
│
◇ Confirm the commit message
│ No
│
└ ✖ process cancelled
Would be nice to have the opportunity to configure a unique message for a batch of files.
Concrete example:
In the exampel below, I introduced a new enum and started using it inside 4 existing files. Then I would like to have a single message in a single commit that is simply "refactor: added SvgElementType constants"
So instead of:
I would like something generating:
git commit -m"refactor: added SvgElementType constants"
The text was updated successfully, but these errors were encountered: