Skip to content

Update build.func - fixed spelling mistake#14047

Open
m1ckywill wants to merge 1 commit intocommunity-scripts:mainfrom
m1ckywill:patch-1
Open

Update build.func - fixed spelling mistake#14047
m1ckywill wants to merge 1 commit intocommunity-scripts:mainfrom
m1ckywill:patch-1

Conversation

@m1ckywill
Copy link
Copy Markdown

✍️ Description

Noted that the OS update prompt had a typo in 'Packages'. This only updates the printed text part of the prompt, no functionality changes.
Unsure of how to test this as I'm not building a script myself, and this seems to be a core part of the tooling for the project.
This is my first commit to a public repo - please let me know if I need to amend anything, and thanks for continuing tteck's legacy.

🔗 Related Issue

None - Hoping it's less burden if I fix the typo myself than raising a bug. But I appreciate it's my first PR so I'm hoping I'm not adding too much to maintainer burden.

Fixes #

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to script metadata (PocketBase/website data).
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

Noted that the OS update prompt had a typo in 'Packages'.
This is my first commit to a public repo - please let me know if I need to amend anything, and thanks for continuing tteck's legacy :)
@m1ckywill m1ckywill requested a review from a team as a code owner April 27, 2026 01:28
Copy link
Copy Markdown
Member

@MickLesk MickLesk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@michelroegl-brunner Always drunk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants