Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .gitmodules
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
[submodule "libs/commcare"]
path = libs/commcare
url = https://github.com/dimagi/commcare-core.git
branch = formplayer
branch = master
Copy link
Member Author

@dannyroberts dannyroberts Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the diff on the libs/commcare change, it looks like the only additional PRs that were merged into master but weren't yet on the formplayer branch at the time that we deleted it were dimagi/commcare-core#1521 and dimagi/commcare-core#1516.

(There are a few other PRs, but they are all PRs that only touch GHA workflows under .github/ and docs/ and so categorically could not break formplayer by incorporating them.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests have of course been run against this, so that adds some level of assurance, but just wanted to raise in case anyone wants to advocate for more deeper testing/QA.

9 changes: 3 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -159,14 +159,11 @@ For PRs that just modify code in the Formplayer repo, submit a PR to Formplayer

#### Contributing changes to commcare

Formplayer also has a dependency on the commcare-core repository. The commcare-core `master` branch is not
stable and Formplayer uses a different branch. The submodule repo `libs/commcare` should always be pointing to
the `formplayer` branch.
Formplayer depends on the commcare-core repository via the `libs/commcare` submodule, which tracks the `master` branch. Cross-repo CI automatically tests formplayer against commcare-core PRs, so no manual cross-testing is needed.

#### Updating the CommCare version
#### Updating the CommCare Version

When updating Formplayer to have a new release of a CommCare version (e.g. 2.34 to 2.35), a PR should be opened from the `commcare_X.Y` branch into
the `formplayer` branch. Once QA has been finished, merge the PR and update the Formplayer submodule.
When updating Formplayer to a new CommCare version (e.g. 2.34 to 2.35), open a PR from the `commcare_X.Y` branch into `master` on commcare-core. Once QA has finished, merge the PR and update the Formplayer submodule.

### IntelliJ Code Style Settings

Expand Down
Loading