From ed6b0eac834986c728ddcbdbbae6501f2850a134 Mon Sep 17 00:00:00 2001
From: Vatsal Gupta <40350810+gvatsal60@users.noreply.github.com>
Date: Sat, 4 Jul 2026 12:31:06 +0530
Subject: [PATCH] Remove CODE_OF_CONDUCT.md and CONTRIBUTING.md

---
 CODE_OF_CONDUCT.md | 26 -----------------------
 CONTRIBUTING.md    | 52 ----------------------------------------------
 2 files changed, 78 deletions(-)
 delete mode 100644 CODE_OF_CONDUCT.md
 delete mode 100644 CONTRIBUTING.md

diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
deleted file mode 100644
index 00108c5..0000000
--- a/CODE_OF_CONDUCT.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment,
-we as contributors and maintainers pledge to make participation in our project
-and our community a harassment-free experience for everyone, regardless of age,
-body size, disability, ethnicity, gender identity and expression,
-level of experience, nationality, personal appearance, race, religion,
-or sexual identity and orientation.
-
-## Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected
-to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting
-the project team at [Github Issues](https://github.com/gvatsal60/Linux-All-In-One-Update-Script/issues).
-All complaints will be reviewed and investigated promptly and fairly.
-
-## Attribution
-
-This [Code of Conduct](https://www.contributor-covenant.org/version/2/0/code_of_conduct)
-is adapted from the Contributor Covenant, version 2.0.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
deleted file mode 100644
index d58abe2..0000000
--- a/CONTRIBUTING.md
+++ /dev/null
@@ -1,52 +0,0 @@
-# Contributing to Linux-All-In-One-Update-Script
-
-Thank you for your interest in contributing to Linux-All-In-One-Update-Script!
-Please follow these guidelines to ensure a smooth process.
-
-## How to Contribute
-
-1. Fork the repository and create your branch from `master`.
-2. Open an issue or feature request on GitHub or pick an existing one.
-3. Work on your changes.
-4. Ensure your code follows our coding standards and conventions.
-5. Test your changes thoroughly.
-6. Submit a pull request referencing the original issue.
-
-## Code Style
-
-### General Guidelines
-
-- **Indentation**: Use 4 spaces for indentation in all code files. Avoid using tabs.
-- **Line Length**: Limit lines to improve readability.
-- **Naming Conventions**: Use meaningful variable and function names.
-Variables should be written in lowercase with underscores separating words
-(e.g., `my_variable`), while function names should use lowercase
-with underscores (e.g., `my_function`).
-
-### Bash Scripts
-
-- **Indentation**: Use 4 spaces for indentation.
-Ensure consistent indentation throughout the script.
-- **POSIX Compliance**: Write scripts to be POSIX-compliant whenever
-possible to ensure compatibility across different Unix-like systems.
-Avoid using non-standard features or extensions specific to a particular shell.
-- **Quoting**: Always quote variable expansions (e.g., `"${variable}"`)
-to prevent issues with spaces or special characters.
-- **Shebang**: Use `#!/bin/sh` for POSIX-compliant scripts. If specific shell
-features are needed, document the specific shell requirement in the script header.
-- **Function Definitions**: Define functions without `function` keyword
-(e.g., `my_function() { ... }`). Consistency is key.
-- **Comments**: Use comments to explain complex logic or provide context.
-Keep comments concise and relevant.
-- **Error Handling**: Include error handling for critical operations.
-- **External Commands**: Prefer using built-in commands and utilities when possible.
-Minimize the use of external commands to improve script portability and performance.
-
-## Reporting Bugs
-
-Please report bugs using the GitHub issue tracker. Include steps to reproduce
-the bug and any relevant error messages.
-
-## Contact
-
-If you have questions or need further assistance, feel free to contact us at [Telegram](https://t.me/gvatsal60).