Skip to content

Commit 69deff9

Browse files
authored
Merge changes to deploy v2
Release v2 of Resonate App with all recent changes
2 parents 153a4dc + 494e305 commit 69deff9

File tree

212 files changed

+32449
-5468
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

212 files changed

+32449
-5468
lines changed
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
name: ⚙️ Configuration Change
2+
description: Suggest modifications to the project’s configuration, such as build tools, CI/CD pipeline adjustments, or environment settings to improve project management or deployment.
3+
4+
body:
5+
- type: textarea
6+
id: configuration-change
7+
attributes:
8+
label: ⚙️ The Configuration Change
9+
description: >
10+
Describe the specific configuration change you propose. What configuration settings or tools need adjustment?
11+
Mention which part of the project this affects, like build tools, CI/CD settings, or deployment configurations.
12+
validations:
13+
required: true
14+
15+
- type: textarea
16+
attributes:
17+
label: Motivation, pitch
18+
description: >
19+
Explain the reason for this configuration change. How will it improve the project's management or deployment process?
20+
For example, will it streamline the CI/CD pipeline, improve build times, or make the project easier to maintain?
21+
validations:
22+
required: true
23+
24+
- type: checkboxes
25+
attributes:
26+
label: Configuration Change Focus Areas
27+
options:
28+
- "Build tools"
29+
- "CI/CD pipeline"
30+
- "Environment settings"
31+
- "Dependency management"
32+
- "Other"
33+
validations:
34+
required: false
35+
36+
- type: markdown
37+
attributes:
38+
value: >
39+
Thank you for your contribution! 🔧 Please provide as much information as possible about the configuration change and how it will benefit the project.
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
name: 🔄 Re-Implementation
2+
description: Suggest rewriting or replacing a part of the codebase for better performance, maintainability, or functionality.
3+
4+
body:
5+
- type: textarea
6+
id: re-implementation
7+
attributes:
8+
label: 🔄 The re-implementation
9+
description: >
10+
A clear and concise description of the part of the system that you think needs re-implementation.
11+
What specific functionality or code block would you like to rewrite or replace? Please explain the issue in detail.
12+
validations:
13+
required: true
14+
15+
- type: textarea
16+
attributes:
17+
label: Motivation, pitch
18+
description: >
19+
Please provide the motivation for re-implementing this part of the code.
20+
Why do you think the current implementation needs to be replaced or rewritten?
21+
E.g., *"The current implementation is slow, hard to maintain, or outdated."* If you have any supporting context or examples, please include them here.
22+
validations:
23+
required: true
24+
25+
- type: checkboxes
26+
attributes:
27+
label: Areas of Focus
28+
options:
29+
- "Performance"
30+
- "Maintainability"
31+
- "Code readability"
32+
- "Functionality improvement"
33+
- "Other"
34+
validations:
35+
required: false
36+
37+
- type: markdown
38+
attributes:
39+
value: >
40+
Thanks for contributing 🎉! Be as detailed as you can in your suggestion. The more information you provide, the easier it will be to understand the need for re-implementation and how it can improve the project!
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
name: 🔧 Refactor to Enhance
2+
description: Suggest a refactor to improve the code's efficiency, readability, or maintainability while keeping its functionality intact.
3+
4+
body:
5+
- type: textarea
6+
id: refactor-to-enhance
7+
attributes:
8+
label: 🔧 The refactor
9+
description: >
10+
Describe the part of the code that you think needs refactoring. What is the current problem or area that could benefit from enhancement?
11+
How do you think refactoring will improve the codebase?
12+
validations:
13+
required: true
14+
15+
- type: textarea
16+
attributes:
17+
label: Motivation, pitch
18+
description: >
19+
Please explain the motivation for this refactor. Why is this refactor needed?
20+
What benefits will it bring to the codebase, such as improved performance, easier maintenance, or better readability?
21+
Provide examples of how the code can be improved if possible.
22+
validations:
23+
required: true
24+
25+
- type: checkboxes
26+
attributes:
27+
label: Refactoring Focus Areas
28+
options:
29+
- "Performance"
30+
- "Code readability"
31+
- "Maintainability"
32+
- "Reducing complexity"
33+
- "Other"
34+
validations:
35+
required: false
36+
37+
- type: markdown
38+
attributes:
39+
value: >
40+
Thank you for suggesting a refactor! 🎉 Be sure to provide as much detail as possible, and help the team understand how the refactor can improve the codebase!
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
name: 🔒 Security Improvement
2+
description: Suggest changes to improve the project's security, including identifying vulnerabilities and proposing measures to harden the codebase.
3+
4+
body:
5+
- type: textarea
6+
id: security-improvement
7+
attributes:
8+
label: 🔒 The Security Improvement
9+
description: >
10+
Describe the security improvement you propose. Identify any potential risks or vulnerabilities in the current setup
11+
and detail the changes required to enhance security. Specify whether it impacts data handling, user authentication, or any external dependencies.
12+
validations:
13+
required: true
14+
15+
- type: textarea
16+
attributes:
17+
label: Motivation, pitch
18+
description: >
19+
Explain the motivation behind this security improvement. How does it protect against security risks, and what kind of
20+
vulnerabilities does it address? Describe how it can prevent unauthorized access, data breaches, or other threats.
21+
validations:
22+
required: true
23+
24+
- type: checkboxes
25+
attributes:
26+
label: Security Improvement Focus Areas
27+
options:
28+
- "Data protection"
29+
- "User authentication"
30+
- "Dependency vulnerabilities"
31+
- "Access control"
32+
- "Other"
33+
validations:
34+
required: false
35+
36+
- type: markdown
37+
attributes:
38+
value: >
39+
Thank you for prioritizing security! 🔒 Be as thorough as possible in identifying potential risks and detailing how your proposal will safeguard the project.
Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
name: Build and Deploy
2+
3+
on:
4+
push:
5+
branches:
6+
- master
7+
pull_request:
8+
types: [closed]
9+
branches:
10+
- master
11+
workflow_dispatch:
12+
13+
jobs:
14+
build:
15+
runs-on: ubuntu-latest
16+
17+
steps:
18+
# 1. Remove Cached Flutter Installation
19+
- name: Remove Cached Flutter Installation
20+
run: rm -rf $HOME/.flutter
21+
22+
- name: Clean up old build files
23+
run: |
24+
rm -rf build/app/outputs/bundle/release/*
25+
26+
# 2. Checkout repository
27+
- name: Checkout code
28+
uses: actions/checkout@v4
29+
30+
# 3. Install Flutter SDK
31+
- name: Install Flutter
32+
uses: subosito/flutter-action@v2
33+
with:
34+
flutter-version: 3.35.2
35+
36+
# 4. Verify Flutter and Dart Versions
37+
- name: Verify Flutter Installation
38+
run: |
39+
flutter --version
40+
dart --version
41+
42+
# 6. Install Flutter dependencies
43+
- name: Install Flutter Dependencies
44+
run: flutter pub get
45+
46+
# 7. Build Android APK
47+
- name: Build Android App Bundle
48+
run: flutter build apk --release --split-per-abi
49+
50+
# 8. Upload build artifacts
51+
- name: Upload APK as an artifact
52+
uses: actions/upload-artifact@v4
53+
with:
54+
name: app-release-apks
55+
path: build/app/outputs/apk/release/*.apk
56+
57+
release:
58+
runs-on: ubuntu-latest
59+
needs: build
60+
permissions:
61+
contents: write
62+
steps:
63+
# 1. Checkout repository
64+
- name: Checkout code
65+
uses: actions/checkout@v4
66+
67+
# 2. Download build artifacts
68+
- name: Download APK
69+
uses: actions/download-artifact@v4
70+
with:
71+
name: app-release-apks
72+
path: build/app/outputs/bundle/release/
73+
74+
# 3. Upload to Github Release
75+
- name: Github Release
76+
uses: ncipollo/[email protected]
77+
with:
78+
allowUpdates: true
79+
artifacts: build/app/outputs/bundle/release/*.apk
80+
artifactContentType: apk
81+
generateReleaseNotes: true
82+
tag: latest_build

.github/workflows/greet_contributors.yml

Lines changed: 59 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@ name: Greet Contributors
22

33
on:
44
issues:
5-
types: [opened]
6-
pull_request:
7-
types: [opened]
5+
types: [opened, closed]
6+
pull_request_target:
7+
types: [opened, closed]
88

99
permissions:
1010
issues: write
@@ -16,34 +16,66 @@ jobs:
1616
runs-on: ubuntu-latest
1717

1818
steps:
19-
- name: Print GitHub context
20-
run: echo "${{ toJson(github) }}"
19+
- name: Handle Opened Issues
20+
if: github.event_name == 'issues' && github.event.action == 'opened'
21+
uses: peter-evans/create-or-update-comment@v4
22+
with:
23+
token: ${{ secrets.GITHUB_TOKEN }}
24+
issue-number: ${{ github.event.issue.number }}
25+
body: |
26+
👋 **Hello @${{ github.actor }}!**
27+
Thank you for opening this issue. Our team will review it soon. 🚀
28+
- If you can, please provide more details like steps to reproduce, expected vs. actual behavior, and screenshots (if applicable). 📌
29+
30+
We appreciate your contribution! 💡
31+
reactions: heart
32+
33+
- name: Handle Closed Issues
34+
if: github.event_name == 'issues' && github.event.action == 'closed'
35+
uses: peter-evans/create-or-update-comment@v4
36+
with:
37+
token: ${{ secrets.GITHUB_TOKEN }}
38+
issue-number: ${{ github.event.issue.number }}
39+
body: |
40+
🔒 **Issue Closed - Thank You, @${{ github.actor }}!**
41+
This issue has been resolved or is no longer relevant.
42+
- If you have further questions, feel free to open a new issue. 💡
2143
22-
- name: Send greeting message for issues
23-
if: github.event_name == 'issues'
24-
uses: actions-ecosystem/[email protected]
25-
continue-on-error: true
44+
Thanks for helping improve the project! 🚀
45+
reactions: |
46+
heart
47+
hooray
48+
49+
- name: Handle Opened PRs
50+
if: github.event_name == 'pull_request_target' && github.event.action == 'opened'
51+
uses: peter-evans/create-or-update-comment@v4
2652
with:
27-
github_token: ${{ secrets.GITHUB_TOKEN }}
28-
repo: ${{ github.repository }}
29-
number: ${{ github.event.issue.number }}
53+
token: ${{ secrets.GITHUB_TOKEN }}
54+
issue-number: ${{ github.event.pull_request.number }}
3055
body: |
31-
Hi @${{ github.event.issue.user.login }}!
32-
Thanks for opening this issue, would you like to work on this?
56+
🎉 **Welcome @${{ github.actor }}!**
57+
Thank you for your pull request! Our team will review it soon. 🔍
58+
- Please ensure your PR follows the contribution guidelines. ✅
59+
- All automated tests should pass before merging. 🔄
60+
- If this PR fixes an issue, link it in the description. 🔗
61+
62+
We appreciate your contribution! 🚀
63+
reactions: |
64+
heart
3365
34-
- name: Send greeting message for PRs
35-
if: github.event_name == 'pull_request'
36-
uses: actions-ecosystem/[email protected]
37-
continue-on-error: true
66+
- name: Handle Closed PRs
67+
if: github.event_name == 'pull_request_target' && github.event.action == 'closed'
68+
uses: peter-evans/create-or-update-comment@v4
3869
with:
39-
github_token: ${{ secrets.GITHUB_TOKEN }}
40-
repo: ${{ github.repository }}
41-
number: ${{ github.event.pull_request.number }}
70+
token: ${{ secrets.GITHUB_TOKEN }}
71+
issue-number: ${{ github.event.pull_request.number }}
4272
body: |
43-
Hi @${{ github.event.pull_request.user.login }}! 🎉
44-
Thanks for opening this pull request. We appreciate your contribution.
73+
✅ **PR Closed - Thank You, @${{ github.event.pull_request.user.login }}!**
74+
- If this PR was merged: **Congratulations! Your contribution is now part of the project.** 🚀
75+
- If this PR was closed without merging: **Don’t worry! You can always improve it and submit again.** 💪
4576
46-
- name: Log completion
47-
run: |
48-
echo "Greeting workflow completed successfully"
49-
echo "Event type: ${{ github.event_name }}"
77+
We appreciate your effort and look forward to more contributions from you! 🤝
78+
reactions: |
79+
heart
80+
hooray
81+
rocket

.github/workflows/run_tests.yml

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
## Github Actions CI workflow to deploy to run automated software tests
2+
name: RUN_SOFTWARE_TESTS
3+
4+
on:
5+
# Run this workflow when any pull requests are opened
6+
workflow_dispatch:
7+
pull_request:
8+
types: [opened, synchronize, reopened]
9+
10+
permissions:
11+
pull-requests: write
12+
contents: read
13+
14+
jobs:
15+
run_tests:
16+
name: Run Software Tests
17+
runs-on: ubuntu-latest
18+
env:
19+
# Setup env variables that will be used throughout the workflow
20+
JAVA_VERSION: 21.0.6
21+
FLUTTER_VERSION: 3.35.2
22+
steps:
23+
# Checkout repository codebase
24+
- name: Checkout the code
25+
uses: actions/checkout@v4
26+
27+
# Setup Java in the VM
28+
- name: Setup Java to compile the Android project
29+
uses: actions/setup-java@v4
30+
with:
31+
distribution: "zulu"
32+
java-version: ${{ env.JAVA_VERSION }}
33+
34+
# Setup Flutter in the VM
35+
- name: Setup Flutter
36+
uses: subosito/flutter-action@v2
37+
with:
38+
flutter-version: ${{ env.FLUTTER_VERSION }}
39+
40+
- name: 📦 Install dependencies
41+
run: flutter pub get
42+
43+
- name: 📉 Run all app tests
44+
run: flutter test

0 commit comments

Comments
 (0)