Add BREAKING CHANGES flag/footer and body message option #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add menu items for setting a body or `BREAKING CHANGES` flag or message. Change the generation of the commit message to reflect the new options.
|
For anyone who wants to try out the changes directly without building them themselves, I have built the extension once and uploaded it as a pre-release version: https://github.com/PxaMMaxP/vscode-git-semantic-commit/releases/tag/v2.1.0 |
…the original state
…the original state
…the original state
…the original state
|
I looked at everything again today and got ESLint configured roughly as originally set. Now all the changes are in line with the project (but probably not pretty yet). I'll take another look at the whole thing when I get a chance. I am already using the modified version of the extension and have not found any errors so far. |
…and VSCode. All style settings have been adopted as far as possible.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #28.
The new functions work, but neither the linter runs correctly, nor can I run the tests locally.
I'll take another look at this myself in the next few days.
Many thanks for any comments!