Skip to content

style(templates): add trailing newlines to styleguide templates #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sherzat3 merged 1 commit into from
Jan 13, 2026
Merged

style(templates): add trailing newlines to styleguide templates #67

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion templates/code_styleguides/go.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,4 +45,4 @@ This document summarizes key rules and best practices from the official "Effecti
- **Explicit Error Handling:** Do not discard errors with the blank identifier (`_`). Check for errors explicitly.
- **`panic`:** Reserved for truly exceptional, unrecoverable situations. Generally, libraries should not panic.

*Source: [Effective Go](https://go.dev/doc/effective_go)*
*Source: [Effective Go](https://go.dev/doc/effective_go)*
2 changes: 1 addition & 1 deletion templates/code_styleguides/html-css.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,4 +46,4 @@ This document summarizes key rules and best practices from the Google HTML/CSS S

**BE CONSISTENT.** When editing code, match the existing style.

*Source: [Google HTML/CSS Style Guide](https://google.github.io/styleguide/htmlcssguide.html)*
*Source: [Google HTML/CSS Style Guide](https://google.github.io/styleguide/htmlcssguide.html)*
2 changes: 1 addition & 1 deletion templates/code_styleguides/javascript.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,4 +48,4 @@ This document summarizes key rules and best practices from the Google JavaScript
- Use `@param`, `@return`, `@override`, `@deprecated`.
- Type annotations are enclosed in braces (e.g., `/** @param {string} userName */`).

*Source: [Google JavaScript Style Guide](https://google.github.io/styleguide/jsguide.html)*
*Source: [Google JavaScript Style Guide](https://google.github.io/styleguide/jsguide.html)*
2 changes: 1 addition & 1 deletion templates/code_styleguides/python.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,4 +34,4 @@ This document summarizes key rules and best practices from the Google Python Sty

**BE CONSISTENT.** When editing code, match the existing style.

*Source: [Google Python Style Guide](https://google.github.io/styleguide/pyguide.html)*
*Source: [Google Python Style Guide](https://google.github.io/styleguide/pyguide.html)*
2 changes: 1 addition & 1 deletion templates/code_styleguides/typescript.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,4 +40,4 @@ This document summarizes key rules and best practices from the Google TypeScript
- **Redundancy:** **Do not declare types in `@param` or `@return` blocks** (e.g., `/** @param {string} user */`). This is redundant in TypeScript.
- **Add Information:** Comments must add information, not just restate the code.

*Source: [Google TypeScript Style Guide](https://google.github.io/styleguide/tsguide.html)*
*Source: [Google TypeScript Style Guide](https://google.github.io/styleguide/tsguide.html)*
Loading