Create an empty public repository named card-stack-android. Do not ask GitHub to generate a README, .gitignore, or license because this source tree already contains them.
Recommended repository metadata:
- Description:
Native Android card stack for Jetpack Compose, derived from leset0ng/card-stack - Topics:
android,kotlin,jetpack-compose,card-stack,gesture,animation,mit-license - Default branch:
main - License: GitHub should automatically detect MIT from
LICENSE
The Kotlin package and Android namespace are owned by the repository maintainer:
io.github.defatestar.cardstack
The corresponding identifiers are:
- Maven groupId:
io.github.defatestar - Library namespace:
io.github.defatestar.cardstack - Demo applicationId:
io.github.defatestar.cardstack.demo
Changing these identifiers after publication is a breaking public API change. The groupId is reserved in the build metadata, but the README must not claim a Maven dependency coordinate until an artifact repository is configured.
From the project root:
git init -b main
git add .
git update-index --chmod=+x gradlew
git commit -m "Initial native Android release"
git remote add origin https://github.com/DefateStar/card-stack-android.git
git push -u origin mainBefore committing, verify that git status --ignored shows local.properties, build directories, APK/AAR files and signing keys as ignored.
After the first push, enable a branch ruleset for main:
- Require a pull request before merging
- Require the
buildjob fromAndroid CI - Block force pushes and branch deletion
The included workflow builds the demo APK and library AAR on pushes and pull requests. Workflow artifacts are temporary test outputs, not permanent public releases.
-
Confirm CI passes on
main. -
Create and push the tag:
git tag -a v0.1.0 -m "Card Stack Android v0.1.0" git push origin v0.1.0 -
Create a GitHub Release from
v0.1.0. -
Attach the tested Demo APK and library AAR.
-
In the release notes, state that this is an independent native Android port derived from
leset0ng/card-stackand licensed under MIT.
Do not upload signing keys or keystore.properties. A public demo APK may use a clearly labeled debug build; production applications should use their own private signing setup.