Transparency of code-push versions
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
At the moment there's no way to tell what's actually deployed via CodePush, which makes collaboration and debugging unnecessarily hard.
* Auto-add the current Git SHA to the release description
* Deny CodePush releases with uncommitted changes, unpushed commits, or when not on the release branch (to avoid accidental promotes)
* Use the locally hosted bundle (by overriding `jsCodeLocation`) when working on the app on a locally connected device (to avoid clashing CodePush staging versions)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the CodePush release flow and the app's jsCodeLocation handling. Review how release descriptions, Git state, the release branch, and locally connected devices are currently determined. Done means all three requested safeguards and transparency behaviors work without accidental CodePush promotes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, react-native
- Domain
- devops, mobile, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100