| name | dev-workflow |
|---|---|
| description | Branch policy, CI, and local build/test commands for contentstack-ios-persistence |
- You are opening a PR, choosing a base branch, or interpreting CI failures
- You need the canonical
pod install/xcodebuildcommands for this repo - You want release or versioning expectations (podspecs, tags)
- Default branch workflow:
.github/workflows/check-branch.ymlblocks merging intomasterunless the PR branch isnext. For changes targetingmaster, open PRs fromnextas described in that workflow’s message. - Use CODEOWNERS for required reviewers when present.
- Install pods:
pod installfrom the repo root (generates/updatesPods/and integrates with the workspace). - Open
ContentstackPersistence.xcworkspace(not the.xcodeprojalone) when working with CocoaPods.
- Build:
xcodebuild -workspace ContentstackPersistence.xcworkspace -scheme ContentstackPersistence -sdk iphonesimulator build - Test:
xcodebuild -workspace ContentstackPersistence.xcworkspace -scheme ContentstackPersistence -destination 'platform=iOS Simulator,name=iPhone 16' test— pick a simulator that exists on your Mac.
- Branch check:
.github/workflows/check-branch.yml— PRs tomasterfrom branches other thannextfail by policy. - SCA:
.github/workflows/sca-scan.yml— Snyksnyk teston PRs (requiresSNYK_TOKENin org secrets). - Policy:
.github/workflows/policy-scan.yml— public repos:SECURITY.mdand license file with current year. - Issues:
.github/workflows/issues-jira.yml— Jira integration for issues.
- Three podspecs at repo root must stay aligned when you bump versions:
ContentstackPersistence.podspec,ContentstackPersistenceCoreData.podspec,ContentstackPersistenceRealm.podspec(sees.versionands.sourcetag). - Talisman:
.talismanrcmay apply to pre-commit secret scanning; do not commit API keys or tokens.