https://github.com/joshuawiebe/scripts
Personal collection of scripts and tools in Python, Bash, and more – for automation, system tasks, and everyday development workflows.
https://github.com/joshuawiebe/scripts
automation bash python scripts
Last synced: about 1 month ago
JSON representation
Personal collection of scripts and tools in Python, Bash, and more – for automation, system tasks, and everyday development workflows.
- Host: GitHub
- URL: https://github.com/joshuawiebe/scripts
- Owner: joshuawiebe
- License: mit
- Created: 2025-07-04T16:18:30.000Z (12 months ago)
- Default Branch: main
- Last Pushed: 2025-08-09T19:03:36.000Z (11 months ago)
- Last Synced: 2025-08-09T21:04:56.603Z (11 months ago)
- Topics: automation, bash, python, scripts
- Language: Python
- Homepage:
- Size: 12.7 KB
- Stars: 3
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# 🛠️ Scripts
This repository contains a curated collection of my personal scripts, written in Python, Bash, and other scripting languages. These scripts are used for automation, system administration, development utilities, and general productivity improvements.
## 📁 Structure
* `bash/` – Shell scripts for automation, system tasks, etc.
* `python/` – Python scripts for tools, utilities, or automation.
* `tools/` – One-off utilities or experimental prototypes.
* `README.md` – Overview of available scripts and usage instructions.
## 🚀 Goals
* Centralized storage of reusable scripts
* Version control and history tracking
* Easy reuse across devices and environments
## 🧩 Planned Additions
* Better logging/output formatting
* Command-line argument parsing
* Script documentation and examples
## 🤝 Contributing
Contributions are welcome! To propose a change:
1. Fork the repository and create a new branch (`git checkout -b feature/my-script`).
2. Add your script or update existing ones under the appropriate folder (`bash/`, `python/`, or `tools/`).
3. Include or update comments/documentation at the top of your script.
4. Commit your changes with a clear message (e.g., `feat: add new backup script`).
5. Push to your fork and open a Pull Request against `main`.
6. Ensure your changes follow the existing code style and pass any CI workflows.
We appreciate detailed descriptions and tests where applicable. Thank you for helping improve this toolbox!
## 📜 License
[MIT](./LICENSE)