IMGIITRoorkee / IMGIITRoorkee/placement-flutter
Decide the fate of the unmerged origin/beta branch
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 3
- Forks
- 10
- Avg merge
- 8d 21h
- Merged PRs (30d)
- 4
Description
Problem
origin/beta is 10 commits ahead of master and 1 behind, and was never merged. It carries lib/themes/theme.dart from "Upgraded to 3.19.0 and added themes" plus iOS build fixes, while master's newer commit is an independent Flutter 3 migration that did not incorporate any of it.
The dark mode and iOS work now queued is at real risk of being done twice.
Where
origin/betacommits62a6a63,abeeef3,44622camastercommit1da4dbc
Expected
The branch is either salvaged into master or deleted, with the decision recorded.
Fix sketch
- Diff
lib/themes/theme.dartand theios/changes against master. - Cherry-pick whatever survives the Flutter 3 migration.
- Delete the branch either way, so it stops looking like pending work.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare commits 62a6a63, abeeef3, and 44622ca with master commit 1da4dbc, starting with lib/themes/theme.dart and the ios/ changes. Check which dark mode and iOS work remains valid after the Flutter 3 migration, then salvage it into master or delete origin/beta and record the decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100