chore(docs): squash-merge docs/update-md-files — Added md files

Author: Rudra-G-23

CHANGELOG.md

@@ -0,0 +1,32 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.  
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+---
+
+## [0.0.1] - 2025-09-25
+
+### Added
+- Initial release of **show-file-tree**.
+- Core functionality: build and display styled file/folder trees directly in the terminal.
+- CLI flags:
+  - `-d, --max-depth` → Limit recursion depth.
+  - `--gitignore / --no-gitignore` → Respect or ignore `.gitignore` files.
+  - `--hidden` → Show hidden files and directories.
+  - `--sort {name,size}` → Sort tree output by name or size.
+  - `--order {asc,desc}` → Control sorting order.
+  - `--size` → Display file/folder sizes.
+  - `--count` → Show file/directory counts inside folders.
+  - `--format {tree,md}` → Output format (tree in terminal or export to Markdown).
+  - `--theme {colorful, monokai, light, nocolor}` → Apply custom color themes.
+  - `--no-icons` → Render plain ASCII trees without icons.
+  - `--mtime-after`, `--mtime-before` → Filter files/folders by modification time.
+  - `--ctime-after`, `--ctime-before` → Filter files/folders by creation time.
+  - `--include`, `--exclude` → Filter paths by glob patterns.
+- General commands:
+  - `--version` → Show package version.
+  - `--about` → Show package information.
+
+
+

CODE_OF_CONDUCT.md

@@ -0,0 +1,38 @@
+# Code of Conduct
+
+Thank you for contributing to **show-file-tree**!  
+We want this project to be welcoming, safe, and inclusive for everyone.
+
+## Our Standards
+
+We are committed to providing a friendly environment where everyone can:
+
+- Be **respectful** and **kind** in all interactions.  
+- Accept constructive feedback with an open mind.  
+- Help others learn and grow by sharing knowledge.  
+- Focus on what is best for the community and project.  
+
+Unacceptable behaviors include:
+
+- Disrespectful or offensive comments.  
+- Personal attacks or harassment.  
+- Spamming, trolling, or disruptive behavior.  
+- Sharing malicious or harmful content.  
+
+## How to Report Issues
+
+If you see behavior that violates this Code of Conduct:
+
+- Open an issue on GitHub **OR**  
+- Contact the maintainer directly   
+
+All reports will be reviewed and handled confidentially.  
+
+## Enforcement
+
+- Violations may result in warnings, temporary bans, or permanent bans from the project, depending on severity.  
+- The maintainer reserves the right to enforce this Code of Conduct.  
+
+## Acknowledgement
+
+This Code of Conduct is inspired by the [Contributor Covenant](https://www.contributor-covenant.org/) but kept short and simple for this project.  

CONTRIBUTING.md

@@ -0,0 +1,107 @@
+# Contributing to show-file-tree
+
+First off, thank you for considering contributing! Your help is greatly appreciated 🙌  
+
+This document outlines the guidelines and best practices for contributing to **show-file-tree**, a small but powerful CLI tool for visualizing file and folder structures.  
+
+---
+
+## 🚀 How Can I Contribute?
+
+### Reporting Bugs
+- First, check if the bug has already been reported under **GitHub Issues**.  
+- If not, open a new issue with:  
+  - A **clear title and description**.  
+  - Steps to reproduce the issue.  
+  - A minimal code sample or test case showing the problem.  
+  - Expected vs actual behavior.  
+
+### Suggesting Enhancements
+- Open a new issue with your enhancement idea.  
+- Provide:  
+  - A **clear description** of the proposed enhancement.  
+  - The **benefit** it brings to users.  
+  - Example use cases, if possible.  
+
+### Pull Requests
+1. **Fork the repo** and create your branch from `main`.  
+2. **Set up your development environment**:  
+
+   ```
+   # Clone your fork
+   git clone https://github.com/YOUR_USERNAME/show-file-tree.git
+   cd show-file-tree
+   ```
+
+   ```
+   # Create a virtual environment and activate it
+   python -m venv .venv
+   source .venv/bin/activate   # (Linux/macOS)
+   .venv\Scripts\activate      # (Windows PowerShell)
+   ```
+   
+   ```
+   # Install dependencies for development
+   pip install -e ".[all]"
+   pip install pytest
+   ```
+
+3. **Make changes** and add tests for your feature or bug fix.
+4. Run the test suite: [**pytest**](https://github.com/pytest-dev/pytest)
+5. Format your code with [**Black**](https://github.com/psf/black) or [**Ruff**](https://github.com/astral-sh/ruff).
+6. Commit your changes with a clear message.
+7. Push your branch and **open a Pull Request** (PR).
+
+---
+
+## 📝 Branching Convention
+
+| Prefix      | Purpose                                   | Example Branch Name     |
+| ----------- | ----------------------------------------- | ----------------------- |
+| `feature/`  | New features or functionality             | `feature/add-cli-tree`  |
+| `fix/`      | Bug fixes or small corrections            | `fix/fix-path-handling` |
+| `docs/`     | Documentation changes                     | `docs/update-readme`    |
+| `wip/`      | Work-in-progress experiments              | `wip/template`          |
+| `chore/`    | Misc tasks like setup, CI, configs        | `chore/add-gitignore`   |
+| `refactor/` | Code restructuring without feature change | `refactor/cleanup-code` |
+
+---
+
+## ✅ Coding Standards
+
+* Follow **[PEP 8](https://peps.python.org/pep-0008/)** style guidelines.
+* Keep functions small, modular, and well-structured.
+* Add **docstrings** to all public modules, functions, classes, and methods.
+* Write **clear, readable commit messages**:
+
+  * `Add: new feature xyz`
+  * `Fix: bug in path handling`
+  * `Docs: update contributing guide`
+
+---
+
+## 🧪 Testing
+
+* Add or update tests for any new code.
+* Run the full test suite with:
+
+  ```bash
+  pytest
+  ```
+* Ensure all tests pass before submitting a PR.
+
+---
+
+## 🙌 Ways to Contribute
+
+* Report bugs
+* Suggest enhancements
+* Submit pull requests (features, bug fixes, documentation)
+* Improve docs (README, examples, etc.)
+
+---
+
+## 📄 License
+
+By contributing, you agree that your contributions will be licensed under the same license as this project (MIT).
+