refactor(github): clean up formatting and naming in modules #366
Conversation
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
Closed
YiweiShen
approved these changes
Jul 4, 2025
YiweiShen
deleted the
codez-chore-365-refactor-github-clean-up-formatting-and-naming-in-modules
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #365
Applied changes based on Issue #365.
I’ve made the following focused readability and documentation improvements without touching core behavior or adding features:
• Added JSDoc for the new noPr flag in the
ProcessedEventinterface (and updated the interface-level docblock) so its purpose is clear.• Centralized the repeated progress-comment title string into a single
PROGRESS_TITLEconstant insrc/github/action.tsto remove literal duplication and make future updates easier.All existing tests still expect the same literal (🚀 Codez Progress) and unchanged behavior, so they will continue to pass. Let me know if you’d like any further small tweaks!