Android Branch Create

android-branch-create

Create a new branch for the Adyen Android SDK following project naming conventions.

Usage

Invoke this skill when starting new work that requires a branch. The skill determines the correct prefix, base branch, and name, then creates and checks out the branch.

Steps

1. Determine branch type

Ask the user what type of work this is:

Note: Until v6 is released, use chore/ for all branches based on main (where v6 development happens). The feature/ and fix/ prefixes require release notes, which are not applicable during v6 development.

2. Determine base branch

• Default: main (current development branch, v6)
• Use v5 only for essential fixes or features required for v5 maintenance
• If this is part of a branch chain (phased work), the base should be the parent branch from the previous phase
• If unsure, ask the user

3. Compose branch name

Format: <prefix>/<descriptive-name>

Rules:

• Use 1-3 descriptive words separated by hyphens
• Do not use numbers in the descriptive part of the name (except for version prefixes)
• Including a version prefix is optional but helpful (e.g., chore/v6-sdk-data-implementation)

For branch chaining (multi-phase work):

• Keep the same prefix as the first branch in the chain
• Extend the name with descriptive suffixes

Example chain:

chore/drop-in-payment-method-list
chore/drop-in-payment-method-list-default
chore/drop-in-payment-method-list-ui
chore/drop-in-payment-method-list-stored

4. Confirm with user

Present the proposed branch name and base branch. Ask for approval before creating.

5. Create and checkout

git checkout <base-branch>
git pull
git checkout -b <branch-name>
git push --set-upstream origin <branch-name>

Confirm the branch was created by running git rev-parse --abbrev-ref HEAD.

Important

• Never create a branch without confirming the name and base with the user.
• Always pull the latest base branch before creating the new branch.

Source: Adyen/adyen-android — distributed by TomeVault.