V2 (#43)

This pull request includes a comprehensive update to the repository, involving additions, deletions, and modifications across various files and directories. The changes aim to enhance the project's structure, documentation, and functionality.

The list of counties and cities has been separated. Districts and rural areas have been added, and everything has been updated according to the latest official changes up to the end of 1402 SH. The project structure has been updated to improve development speed after 6 years.

Author: sajaddp

.github/workflows/stale.yml

@@ -7,21 +7,20 @@ name: Mark stale issues and pull requests
 
 on:
   schedule:
-  - cron: '38 8 * * *'
+    - cron: "38 8 * * *"
 
 jobs:
   stale:
-
     runs-on: ubuntu-latest
     permissions:
       issues: write
       pull-requests: write
 
     steps:
-    - uses: actions/stale@v5
-      with:
-        repo-token: ${{ secrets.GITHUB_TOKEN }}
-        stale-issue-message: 'Stale issue message'
-        stale-pr-message: 'Stale pull request message'
-        stale-issue-label: 'no-issue-activity'
-        stale-pr-label: 'no-pr-activity'
+      - uses: actions/stale@v5
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          stale-issue-message: "Stale issue message"
+          stale-pr-message: "Stale pull request message"
+          stale-issue-label: "no-issue-activity"
+          stale-pr-label: "no-pr-activity"

CONTRIBUTING.md

@@ -0,0 +1,91 @@
+# راهنمای مشارکت در پروژه
+
+از مشارکت شما در این پروژه صمیمانه استقبال می‌کنیم. لطفاً پیش از ارسال هرگونه درخواست تغییر، این راهنما را با دقت مطالعه کنید تا با فرآیند استاندارد مشارکت آشنا شوید.
+
+## نحوه مشارکت
+
+1. **فورک کردن مخزن اصلی**  
+   ابتدا مخزن اصلی را فورک کنید تا یک نسخهی کپی‌شده از آن در حساب کاربری شما ایجاد شود.
+
+2. **ایجاد شاخهی مجزا برای تغییرات**  
+   در مخزن فورک‌شده، یک شاخهی جدید برای تغییرات خود ایجاد کنید:
+
+   ```bash
+   git checkout -b feature/YourFeatureName
+   ```
+
+3. **اعمال تغییرات موردنظر**  
+   کد خود را مطابق با استانداردهای پروژه و به صورت تمیز و خوانا تغییر دهید.
+
+4. **بررسی و کامیت تغییرات**  
+   پس از اعمال تغییرات، آن‌ها را بررسی کرده و با پیامی واضح و دقیق کامیت کنید:
+
+   ```bash
+   git commit -m "Add: [شرح مختصر تغییر انجام‌شده]"
+   ```
+
+5. **پوش کردن به مخزن فورک‌شده**  
+   تغییرات خود را به شاخهی ایجادشده در مخزن فورک‌شده پوش کنید:
+
+   ```bash
+   git push origin feature/YourFeatureName
+   ```
+
+6. **ایجاد Pull Request (PR)**  
+   در گیت‌هاب، از شاخهی خود یک Pull Request به شاخهی اصلی مخزن پروژه ایجاد کرده و در توضیحات آن، هدف و جزئیات تغییرات را بنویسید.
+
+## قوانین و الزامات مشارکت
+
+- کد شما باید مطابق با الگوی کدنویسی تعریف‌شده در پروژه باشد.
+- قبل از ارسال Pull Request اطمینان حاصل کنید که همهی تست‌ها با موفقیت پس شده‌اند.
+- پیام‌های کامیت باید روشن، مختصر و منطقی باشند.
+- از ایجاد تغییرات نامرتبط با موضوع شاخه خودداری کنید.
+- در صورت نیاز، مستندات مرتبط با تغییرات خود را به‌روزرسانی نمایید.
+
+## گزارش مشکلات (Issues)
+
+در صورت مواجهه با باگ، نقص عملکرد یا پیشنهاد ویژگی جدید، لطفاً یک Issue جدید باز کرده و شرح دقیقی از مشکل یا پیشنهاد ارائه دهید. درج مراحل بازتولید مشکل (در صورت وجود) کمک بزرگی به رفع سریع‌تر آن خواهد کرد.
+
+---
+
+## Contribution Guidelines
+
+We sincerely welcome your contributions to this project. Before submitting any changes, please carefully read this guide to understand the standard contribution process.
+
+## How to Contribute
+
+1. **Fork the main repository**  
+   Start by forking the main repository to create a copy under your own GitHub account.
+
+2. **Create a dedicated branch for your changes**  
+   In your forked repository, create a new branch specifically for your changes:
+
+   ```bash
+   git checkout -b feature/YourFeatureName
+   ```
+
+3. **Apply your intended changes**  
+   Modify the code according to the project's standards, keeping it clean and readable.
+
+4. **Review and commit changes**  
+   After making your changes, review them and commit with a clear and meaningful message:
+
+   ```bash
+   git commit -m "Add: [Short description of the changes made]"
+   ```
+
+5. **Push to the forked repository**  
+   Push your changes to the newly created branch in your forked repository:
+
+   ```bash
+   git push origin feature/YourFeatureName
+   ```
+
+6. **Create a Pull Request (PR)**  
+   On GitHub, open a Pull Request from your branch to the main branch of the project repository. Clearly describe the purpose and details of your changes.
+
+## Contribution Rules and Requirements
+
+- Ensure that your code follows the project's coding conventions and style.
+- Make sure all tests pass successfully before submitting a Pull Request.
+- Commit messages must be

LICENSE

@@ -1,7 +1,7 @@
                     GNU GENERAL PUBLIC LICENSE
                        Version 3, 29 June 2007
 
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
  Everyone is permitted to copy and distribute verbatim copies
  of this license document, but changing it is not allowed.
 
@@ -645,30 +645,30 @@ the "copyright" line and a pointer to where the full notice is found.
     GNU General Public License for more details.
 
     You should have received a copy of the GNU General Public License
-    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 Also add information on how to contact you by electronic and paper mail.
 
   If the program does terminal interaction, make it output a short
 notice like this when it starts in an interactive mode:
 
-    <program>  Copyright (C) <year>  <name of author>
+    List of cities in Iran  Copyright (C) 2025  Sajad Dehshiri (sajaddp)
     This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
     This is free software, and you are welcome to redistribute it
     under certain conditions; type `show c' for details.
 
-The hypothetical commands `show w' and `show c' should show the appropriate
+The hypothetical commands `show w' and`show c' should show the appropriate
 parts of the General Public License.  Of course, your program's commands
 might be different; for a GUI interface, you would use an "about box".
 
   You should also get your employer (if you work as a programmer) or school,
 if any, to sign a "copyright disclaimer" for the program, if necessary.
 For more information on this, and how to apply and follow the GNU GPL, see
-<http://www.gnu.org/licenses/>.
+<https://www.gnu.org/licenses/>.
 
   The GNU General Public License does not permit incorporating your program
 into proprietary programs.  If your program is a subroutine library, you
 may consider it more useful to permit linking proprietary applications with
 the library.  If this is what you want to do, use the GNU Lesser General
 Public License instead of this License.  But first, please read
-<http://www.gnu.org/philosophy/why-not-lgpl.html>.
+<https://www.gnu.org/licenses/why-not-lgpl.html>.