Fix .hbs file copyright parsing by supporting indented content#188
Merged
CreatorHead merged 1 commit intomainfrom Feb 3, 2026
Merged
Fix .hbs file copyright parsing by supporting indented content#188CreatorHead merged 1 commit intomainfrom
CreatorHead merged 1 commit intomainfrom
Conversation
- Add support for handlebars (.hbs) files with {{! ... }} multi-line comments
- Copyright lines in .hbs files are indented with spaces but lack direct comment prefixes
- Added ' ' (two spaces) to commentPrefixes array to handle indented content within multi-line comments
- Added comprehensive test coverage for handlebars copyright parsing
- All existing tests continue to pass
Revert copyright year change in update.go
- Change back from 2022, 2026 to 2023, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Revert copyright year change in update.go
🛠️ Description
🔗 External Links
👍 Definition of Done
🤔 Can be merged upon approval?
✅
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.