Skip to content

docs: update formatting #159

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
ahpook merged 1 commit into from
Jul 1, 2025
Merged

docs: update formatting #159

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
1 change: 0 additions & 1 deletion policies/releasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,6 @@ The following steps should be taken to release and maintain your open source pro
- **SECURITY.md file** including instructions that enable users to privately report security vulnerabilities
found in your project.
4. **Prepare the code for release**.

- **Code license**. MIT is the preferred license - other licenses must be cleared with legal.
- **Remove sensitive assets**.
- Remove any reference in the code to internal or confidential information, including internal paths, tools, codenames, proprietary fonts, internal telemetry and email aliases.
Expand Down