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: README.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,18 +60,20 @@ APP package name is `com.github.metacubex.clash.meta`
60
60
- Import a profile
61
61
- URL Scheme `clash://install-config?url=<encoded URI>` or `clashmeta://install-config?url=<encoded URI>`
62
62
63
-
### Kernel Contribution
63
+
### Contribution and Project Maintainance
64
+
65
+
#### Meta Kernel
64
66
65
67
- CMFA uses the kernel from `android-real` branch under `MetaCubeX/Clash.Meta`, which is a merge of the main `Alpha` branch and `android-open`.
66
68
- If you want to contribute to the kernel, make PRs to `Alpha` branch of the Meta kernel repository.
67
69
- If you want to contribute Android-specific patches to the kernel, make PRs to `android-open` branch of the Meta kernel repository.
68
70
69
-
###Project Maintainance
71
+
####Maintainance
70
72
71
73
- When `MetaCubeX/Clash.Meta` kernel is updated to a new version, the `Update Dependencies` actions in this repo will be triggered automatically.
72
74
- It will pull the new version of the meta kernel, update all the golang dependencies, and create a PR without manual intervention.
73
75
- If there is any compile error in PR, you need to fix it before merging. Alternatively, you may merge the PR directly.
74
-
- Manually triggering `Build Pre-Release` actions will automatically compile and publish a `PreRelease` version.
75
-
- Manually triggering `Build Release` actions will automatically compile, tag and publish a `Release` version.
76
-
-There is an option `Auto bump project version` in trigger widget. If this option is checked and triggered, the `versionName` and `versionCode` in `build.gradle.kts` will be bumped first, then do the common build release process.
77
-
-This option is intended for quickly update and release a new version online, without pulling the repository locally and work around by manual.
76
+
- Manually triggering `Build Pre-Release` actions will compile and publish a `PreRelease` version.
77
+
- Manually triggering `Build Release` actions will compile, tag and publish a `Release` version.
78
+
-You must fill the blank `Release Tag` with the tag you want to release in the format of `v1.2.3`.
79
+
-`versionName`and `versionCode` in `build.gradle.kts` will be automatically bumped to the tag you filled above.
0 commit comments