Skip to content

Commit 42055ef

Browse files
pranjal29092005pranjal29092005
committed
chore: resolve merge conflicts with dev branch
2 parents 3889a6c + 397e55c commit 42055ef

File tree

76 files changed

+10401
-3127
lines changed

Some content is hidden

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

76 files changed

+10401
-3127
lines changed

‎.github/ISSUE_TEMPLATE/ci_cd_tooling.yml‎

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
name: 🔧 CI/CD & Tooling
2+
description: Improve CI/CD workflows, build scripts, or development tools
3+
title: "CI/CD: <Please write a comprehensive title after the 'CI/CD: ' prefix>"
4+
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: >
9+
Use this template for proposing improvements to CI/CD pipelines, GitHub Actions workflows, build scripts, linting, formatting, or other development tools.
10+
11+
- type: textarea
12+
id: cicd-tooling-change
13+
attributes:
14+
label: 🔧 The CI/CD or Tooling Change
15+
description: >
16+
Describe the CI/CD or tooling change you're proposing. Which workflow, script, or tool needs improvement?
17+
placeholder: |
18+
Update GitHub Actions workflow to cache dependencies and reduce build time.
19+
validations:
20+
required: true
21+
22+
- type: dropdown
23+
id: tooling-category
24+
attributes:
25+
label: Category
26+
description: What category does this change fall into?
27+
options:
28+
- "GitHub Actions workflow"
29+
- "Build scripts"
30+
- "Linting/formatting"
31+
- "Development environment"
32+
- "Deployment pipeline"
33+
- "Other tooling"
34+
validations:
35+
required: true
36+
37+
- type: textarea
38+
attributes:
39+
label: Motivation
40+
description: >
41+
Why is this change needed? How will it improve the development or deployment process?
42+
placeholder: |
43+
- Current CI builds take 15+ minutes
44+
- Caching dependencies will reduce build time to ~5 minutes
45+
- Faster feedback for contributors
46+
validations:
47+
required: true
48+
49+
- type: textarea
50+
attributes:
51+
label: Impact on Contributors
52+
description: >
53+
How will this change affect contributors? Will they need to update their local setup or workflows?
54+
placeholder: |
55+
No impact on local development. Contributors will see faster CI feedback.
56+
validations:
57+
required: false
58+
59+
- type: checkboxes
60+
attributes:
61+
label: Tooling Focus Areas
62+
description: What aspects does this change address?
63+
options:
64+
- label: "Build performance"
65+
- label: "Code quality automation"
66+
- label: "Deployment automation"
67+
- label: "Developer experience"
68+
- label: "CI/CD reliability"
69+
- label: "Other"
70+
validations:
71+
required: false
72+
73+
- type: markdown
74+
attributes:
75+
value: >
76+
Thanks for improving Resonate's development workflow! 🔧

‎.github/ISSUE_TEMPLATE/dependency_update.yml‎

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
name: 📦 Dependency Update
2+
description: Update project dependencies or address deprecation warnings
3+
title: "DEPS: <Please write a comprehensive title after the 'DEPS: ' prefix>"
4+
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: >
9+
Use this template for proposing dependency upgrades, security updates, or addressing deprecation warnings.
10+
11+
- type: input
12+
id: package-name
13+
attributes:
14+
label: 📦 Package Name
15+
description: >
16+
Which package or dependency needs to be updated?
17+
placeholder: "appwrite"
18+
validations:
19+
required: true
20+
21+
- type: input
22+
id: current-version
23+
attributes:
24+
label: Current Version
25+
description: >
26+
What is the current version being used?
27+
placeholder: "1.6.0"
28+
validations:
29+
required: true
30+
31+
- type: input
32+
id: target-version
33+
attributes:
34+
label: Target Version
35+
description: >
36+
What version do you propose updating to?
37+
placeholder: "1.8.0"
38+
validations:
39+
required: true
40+
41+
- type: dropdown
42+
id: update-reason
43+
attributes:
44+
label: Update Reason
45+
description: Why is this update needed?
46+
options:
47+
- "Security vulnerability fix"
48+
- "Deprecation warning"
49+
- "New features needed"
50+
- "Bug fix in newer version"
51+
- "Performance improvement"
52+
- "Compatibility requirement"
53+
- "Other"
54+
validations:
55+
required: true
56+
57+
- type: textarea
58+
attributes:
59+
label: Breaking Changes
60+
description: >
61+
Does this update include any breaking changes? If yes, describe what needs to be updated in the codebase.
62+
placeholder: |
63+
- API endpoint structure changed
64+
- Method signatures updated
65+
- Configuration format modified
66+
validations:
67+
required: false
68+
69+
- type: textarea
70+
attributes:
71+
label: Additional Context
72+
description: >
73+
Any additional information about this dependency update? (e.g., changelog link, migration guide, testing notes)
74+
placeholder: |
75+
Changelog: https://github.com/appwrite/sdk-for-flutter/releases/tag/1.8.0
76+
Migration guide: https://appwrite.io/docs/migration-guide
77+
validations:
78+
required: false
79+
80+
- type: markdown
81+
attributes:
82+
value: >
83+
Thanks for keeping Resonate's dependencies up to date! 📦

‎.github/ISSUE_TEMPLATE/new_release.yml‎

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
name: ✨ New Release
2+
description: Prepare for a new version release of Resonate
3+
title: "RELEASE: <Please write a comprehensive title after the 'RELEASE: ' prefix>"
4+
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: >
9+
Use this template for tasks related to preparing a new release, including version bumps, changelog updates, and release notes preparation.
10+
11+
- type: input
12+
id: release-version
13+
attributes:
14+
label: 📦 Release Version
15+
description: >
16+
What version are you preparing to release? (e.g., v1.2.0, v2.0.0-beta.1)
17+
placeholder: "v1.2.0"
18+
validations:
19+
required: true
20+
21+
- type: textarea
22+
id: changelog-summary
23+
attributes:
24+
label: 📝 Changelog Summary
25+
description: >
26+
Provide a brief summary of the key changes in this release. What's new, what's fixed, what's improved?
27+
placeholder: |
28+
- Added new feature X
29+
- Fixed bug Y
30+
- Improved performance of Z
31+
validations:
32+
required: true
33+
34+
- type: checkboxes
35+
attributes:
36+
label: Breaking Changes
37+
description: Does this release include any breaking changes?
38+
options:
39+
- label: "This release includes breaking changes"
40+
required: false
41+
42+
- type: textarea
43+
attributes:
44+
label: Release Checklist
45+
description: >
46+
List any tasks that need to be completed before this release can be published.
47+
placeholder: |
48+
- [ ] Update version in pubspec.yaml
49+
- [ ] Update CHANGELOG.md
50+
- [ ] Create release notes
51+
- [ ] Tag the release
52+
- [ ] Test on all platforms
53+
validations:
54+
required: false
55+
56+
- type: markdown
57+
attributes:
58+
value: >
59+
Thanks for helping with the release process! 🎉

‎.github/ISSUE_TEMPLATE/testing.yml‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
name: 🧪 Testing
2+
description: Improve test coverage or fix testing infrastructure
3+
title: "TEST: <Please write a comprehensive title after the 'TEST: ' prefix>"
4+
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: >
9+
Use this template for proposing test improvements, adding new tests, or fixing test infrastructure issues.
10+
11+
- type: dropdown
12+
id: test-type
13+
attributes:
14+
label: 🧪 Test Type
15+
description: What type of testing does this relate to?
16+
options:
17+
- "Unit tests"
18+
- "Integration tests"
19+
- "Widget tests"
20+
- "End-to-end tests"
21+
- "Test infrastructure"
22+
- "Other"
23+
validations:
24+
required: true
25+
26+
- type: textarea
27+
id: testing-improvement
28+
attributes:
29+
label: 🧪 The Testing Improvement
30+
description: >
31+
Describe the testing improvement you're proposing. What area of the codebase needs better test coverage or what test issues need fixing?
32+
placeholder: |
33+
Add unit tests for the authentication service to improve coverage from 45% to 80%.
34+
validations:
35+
required: true
36+
37+
- type: textarea
38+
attributes:
39+
label: Motivation
40+
description: >
41+
Why is this testing improvement needed? What problems will it solve or prevent?
42+
placeholder: |
43+
- Current coverage is low, making refactoring risky
44+
- Recent bugs could have been caught by tests
45+
- Flaky tests are causing CI failures
46+
validations:
47+
required: true
48+
49+
- type: checkboxes
50+
attributes:
51+
label: Testing Focus Areas
52+
description: What aspects does this improvement address?
53+
options:
54+
- label: "Increase test coverage"
55+
- label: "Fix flaky tests"
56+
- label: "Improve test performance"
57+
- label: "Add missing test cases"
58+
- label: "Update test infrastructure"
59+
- label: "Other"
60+
validations:
61+
required: false
62+
63+
- type: markdown
64+
attributes:
65+
value: >
66+
Thanks for improving Resonate's test quality! 🧪

‎.github/ISSUE_TEMPLATE/translation.yml‎

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
name: 🌐 Translation
2+
description: Add or improve translations for internationalization (i18n)
3+
title: "i18n: <Please write a comprehensive title after the 'i18n: ' prefix>"
4+
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: >
9+
Use this template for adding new language translations or fixing existing translation issues.
10+
11+
- type: input
12+
id: language
13+
attributes:
14+
label: 🌍 Language
15+
description: >
16+
Which language are you adding or updating? (e.g., Spanish, French, Hindi, Punjabi)
17+
placeholder: "Spanish (es)"
18+
validations:
19+
required: true
20+
21+
- type: dropdown
22+
id: translation-type
23+
attributes:
24+
label: Translation Type
25+
description: What type of translation work is this?
26+
options:
27+
- "New language addition"
28+
- "Fix existing translation"
29+
- "Update outdated translation"
30+
- "Complete partial translation"
31+
validations:
32+
required: true
33+
34+
- type: textarea
35+
attributes:
36+
label: Translation Scope
37+
description: >
38+
What parts of the app will be translated? (e.g., all UI strings, specific screens, error messages)
39+
placeholder: |
40+
- All main navigation strings
41+
- Home screen content
42+
- Settings menu
43+
validations:
44+
required: true
45+
46+
- type: textarea
47+
attributes:
48+
label: Additional Context
49+
description: >
50+
Any additional information about this translation? (e.g., regional variant, reference materials used, native speaker review)
51+
placeholder: |
52+
I am a native speaker and have reviewed all strings for cultural appropriateness.
53+
validations:
54+
required: false
55+
56+
- type: markdown
57+
attributes:
58+
value: >
59+
Thanks for helping make Resonate accessible to more people! 🌐

0 commit comments

Comments
 (0)