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
Fix clippy lints across codebase
Replace println! with ui helper functions for consistent output handling
and respect quiet mode throughout the application. Update all file
analyzers to use multi-line regex formatting for better readability.
Add missing std::fmt::Write imports and use write!/writeln! macros
instead of string concatenation for better performance.
Key changes:
- Replace println! with ui::print_message, ui::print_newline, and
ui::print_bordered_content functions
- Import std::fmt::Write as FmtWrite to avoid naming conflicts
- Use write!/writeln! macros instead of push_str for string building
- Format multi-line regex patterns consistently across file analyzers
- Replace once_cell lazy_static with std::sync::LazyLock
- Update logger static variables to use consistent formatting
Affected areas include UI output, string formatting, regex definitions,
and static variable declarations across 33 files.
prompt.push_str("Focus on the impact and benefits of the changes to users and developers. ");
411
-
prompt.push_str("Highlight key features, improvements, and fixes. ");
412
-
prompt.push_str("Include a high-level summary of the release, major changes, and any breaking changes or important upgrade notes. ");
413
-
prompt.push_str("Group changes into meaningful sections and explain the rationale behind important changes when possible. ");
414
-
prompt.push_str("Include associated issue numbers and pull request numbers when relevant. ");
389
+
)
390
+
.expect("writing to string should never fail");
415
391
416
392
match detail_level {
417
393
DetailLevel::Minimal => {
418
394
prompt.push_str(
419
-
"Keep the release notes brief and focused on the most significant changes. ",
395
+
"Keep the release notes brief and focus only on the most critical changes. ",
420
396
);
421
397
}
422
398
DetailLevel::Standard => {
423
-
prompt.push_str("Provide a balanced overview of all important changes, with some details on major features or fixes. ");
399
+
prompt.push_str("Provide a balanced overview of all significant changes. ");
424
400
}
425
401
DetailLevel::Detailed => {
426
-
prompt.push_str("Include detailed explanations of changes, their rationale, and potential impact on the project or workflow. ");
427
-
prompt.push_str("Provide context for technical changes and include file-level details where relevant. ");
402
+
prompt.push_str("Include detailed explanations and context for all changes. ");
428
403
}
429
404
}
430
405
406
+
prompt.push_str("Focus on user-facing changes and highlight the most impactful improvements, new features, and bug fixes. ");
407
+
prompt.push_str("Structure the notes to be clear and actionable for users and developers. ");
408
+
prompt.push_str("Include upgrade notes for any breaking changes. ");
409
+
prompt.push_str("Reference associated issues and pull requests where relevant. ");
410
+
431
411
if readme_summary.is_some(){
432
-
prompt.push_str("Ensure the release notes align with the project's overall goals and main features as described in the README summary. ");
412
+
prompt.push_str("Use the README summary to understand the project context and ensure the release notes align with the project's purpose and user base. ");
433
413
}
434
414
435
-
prompt.push_str(
436
-
"Incorporate the overall metrics to give context about the scope of this release. ",
437
-
);
438
-
prompt.push_str("Pay special attention to changes with high impact scores, as they are likely to be the most significant. ");
0 commit comments