You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLAUDE.md
+23-2Lines changed: 23 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,29 @@ If an upstream merge changes either of these, revert immediately and do not ship
13
13
14
14
## Git workflow
15
15
16
-
After completing any fix or feature on the `glucodroid` branch, always commit and push the changes immediately.
17
-
Use a clear commit message, then run `git push`.
16
+
Never push directly to `origin/glucodroid`. All fixes and features go through a PR:
17
+
18
+
1. Create a feature branch off `glucodroid` (e.g. `fix/<short-name>` or `feat/<short-name>`).
19
+
2. Commit the changes on that branch.
20
+
3. Push the feature branch: `git push -u origin <branch>`.
21
+
4. Open a PR with `gh pr create --base glucodroid --head <branch> --title "..." --body "..."`.
22
+
5. Merge with `gh pr merge <n> --squash --delete-branch` once CI is green.
23
+
6. The `glucodroid` branch itself is updated by the squash merge — never `git push` to it directly.
24
+
25
+
`origin` is `robster7674/glucodroid` (this repo). `upstream` is `ctqvva/JugglucoNG` — **never push to upstream** under any circumstances; it is read-only mirror reference.
26
+
27
+
## Release process
28
+
29
+
Every release follows these steps in order — do not skip any:
30
+
31
+
1. Bump `versionName` / `versionCode` in `Common/build.gradle` defaultConfig.
3. Copy APK to `~/Downloads/glucodroid.apk` (exact filename — never rename).
34
+
4. Commit the version bump + any other release-blocker fixes on the feature branch.
35
+
5. Open and merge the PR into `glucodroid` (squash, delete branch).
36
+
6. Tag the merged commit on `glucodroid`: `git tag -a vX.Y.Z -m "vX.Y.Z" && git push origin vX.Y.Z`.
37
+
7. Create the GitHub release with `gh release create vX.Y.Z --prerelease --title "vX.Y.Z" --notes-file <notes.md> --target glucodroid`. (If `gh release create` fails on scope, use the REST API with `gh auth token`.)
38
+
8.**Upload the APK as a release asset** — `~/Downloads/glucodroid.apk` MUST be attached to the release as `glucodroid.apk`. A release with notes but no APK is incomplete and the release is not done. Verify `browser_download_url` is present in the upload response.
0 commit comments