upload

.github/.pull_request_template.md

@@ -0,0 +1,44 @@
+# Pull Request for Renamify
+
+## Description
+
+Please provide a detailed summary of the changes, including the purpose and context. Reference any related issues or discussions.
+
+### Type of Change
+
+- [ ] Bug Fix
+- [ ] New Feature
+- [ ] UI Update
+- [ ] Performance Improvement
+- [ ] Documentation Update
+- [ ] Dependency Update
+- [ ] Other (please specify):
+
+## Checklist
+
+Before submitting this pull request, ensure the following tasks have been completed:
+
+- [ ] Changes have been tested locally using `vite dev` or equivalent.
+- [ ] Associated documentation has been updated to reflect the changes.
+- [ ] This PR resolves any linked issues (**issue ID:** #{ID}).
+- [ ] A clear and detailed description of the problem, solution, and implementation approach is provided.
+- [ ] Code follows the project's coding standards and guidelines.
+- [ ] No errors or warnings are present in the console.
+- [ ] Relevant tests have been added or updated and pass locally.
+- [ ] All merge conflicts are resolved.
+
+## Testing Instructions
+
+Please describe the testing steps and any relevant configurations for verifying the changes:
+
+1.
+2.
+3.
+
+## Dependencies and Updates
+
+Include any updates to dependencies, frameworks, or tooling (e.g., `tailwindcss`, `vue-router`, `pinia`) and their impact on the project.
+
+## Additional Comments
+
+Provide any additional context, considerations, or follow-up tasks related to this pull request.

.github/ISSUE_TEMPLATE/bug_fix.yml

@@ -0,0 +1,34 @@
+name: Bug Report
+description: Report a bug or an issue with this project.
+labels: bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for reporting a bug! Please provide the following information.
+  - type: input
+    id: title
+    attributes:
+      label: Short description
+      description: A simple title for the issue.
+      placeholder: Bug - Something is not working
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Provide a detailed description of the bug, you found.
+      placeholder: Steps to recreate or reproduce expected behavior, actual behavior.
+    validations:
+      required: true
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Severity
+      description: How severe is the issue?
+      options:
+        - Low
+        - Medium
+        - High
+        - Critical

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,40 @@
+name: Feature Request
+description: Suggest a new feature or enhancement for this project.
+labels: enhancement
+body:
+  - type: markdown
+    attributes:
+      value: |
+        We appreciate your ideas for improving this project! Please fill in the following:
+  - type: input
+    id: title
+    attributes:
+      label: Feature title
+      description: A short title summarizing the feature.
+      placeholder: Add X functionality
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Provide a detailed description of the requested feature.
+      placeholder: Describe the feature, its use cases, and benefits.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives
+      description: Describe any alternative solutions or approaches you've considered.
+      placeholder: Provide some alternative solutions, if applicable.
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: How important is this feature?
+      options:
+        - Low
+        - Medium
+        - High
+        - Critical

.github/ISSUE_TEMPLATE/question.yml

@@ -0,0 +1,24 @@
+name: Question
+description: Ask a question related to this project.
+labels: question
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Have a question? Please provide as much context as possible.
+  - type: input
+    id: title
+    attributes:
+      label: Question title
+      description: A brief summary of your question.
+      placeholder: Question about {feature}
+    validations:
+      required: true
+  - type: textarea
+    id: details
+    attributes:
+      label: Question details
+      description: A little Elaboration of your question.
+      placeholder: Provide additional detailed information.
+    validations:
+      required: true

.github/workflows/debug.yml

@@ -33,4 +33,4 @@ jobs:
           name: debug-artifacts
           path: |
             ${{ steps.debugAab.outputs.aabfile }}
-            ${{ steps.debugApk.outputs.apkfile }}
+            ${{ steps.debugApk.outputs.apkfile }}

.github/workflows/format.yml

@@ -21,10 +21,11 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v3
 
-      - name: Set up Node.js
-        uses: actions/setup-node@v3
+      - name: Setup Java
+        uses: actions/setup-java@v3
         with:
-          node-version: '16'
+          distribution: temurin
+          java-version: 17
 
       - name: Configure Prettier
         run: |
@@ -44,11 +45,12 @@ jobs:
       - name: Install Prettier with plugins
         run: |
           npm i -D prettier prettier-plugin-java
-
+          
       - name: Format all files
         run: |
           npx prettier -w **/*.md
-          npx prettier -w **/*.java  --plugin=prettier-plugin-java
+          npx prettier -w **/*.java --plugin=prettier-plugin-java
+          find . -type f -name "*.xml" -exec java -jar tools/android-xml-formatter.jar --indention 2 --attribute-indention 2 {} \;
 
       - name: Clean up unnecessary files
         run: |
@@ -57,9 +59,13 @@ jobs:
           rm -f package-lock.json
           rm -f .prettierrc
           rm -f .prettierignore
+
       - name: Commit changes
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
           git config --global user.name "GitHub Actions"
-          git config --global user.email "actions@github.com"
+          git config --global user.email "actions@github.com"
+          git add .
+          git commit -m "auto-format" || echo "No changes to commit"
+          git push

.github/workflows/release.yml

@@ -70,4 +70,4 @@ jobs:
           path: |
             ${{ env.aabfile }}
             ${{ env.apkfile }}
-            release-output.zip
+            release-output.zip

.github/workflows/respond.yml

@@ -0,0 +1,24 @@
+on:
+  fork:
+  push:
+    branches: [develop]
+  issues:
+    types: [opened]
+  issue_comment:
+    types: [created]
+  pull_request_target:
+    types: [opened]
+  pull_request_review_comment:
+    types: [created]
+
+jobs:
+  welcome:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v1
+      - uses: EddieHubCommunity/gh-action-community/src/welcome@main
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          issue-message: '<h1>Feeling great to have your contribution for this project</h1> Welcome to our project'
+          pr-message: '<h1>Feeling great to have your contribution for this project</h1> Welcome to our project'
+          footer: 'Our developers will respond you as soon as possible. Any questions? Let us know.'

CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Our Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our project and community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We commit to acting and interacting in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people.
+- Being respectful of differing opinions, viewpoints, and experiences.
+- Giving and gracefully accepting constructive feedback.
+- Focusing on what is best for the community.
+- Showing respect for fellow contributors.
+
+Examples of unacceptable behavior include:
+
+- The use of unapropriate language.
+- Trolling, insulting or derogatory comments, and personal or political attacks.
+- Public or private harassment.
+- Publishing others’ private information without their explicit permission.
+- Other conduct that could reasonably be considered inappropriate in a professional setting.
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces and when an individual is representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team at [madnifm347@outlook.com](mailto:madnifm347@outlook.com). All complaints will be reviewed and investigated promptly and fairly.
+
+Community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).