Change GitHub + Anaconda orgs

[pdiakumis]

Moving to tidywf.

[pdiakumis]

@claude what do you think about these changes?

[claude]

Claude finished @pdiakumis's task in 1m 3s —— View job

---

Review of PR #39: Change GitHub + Anaconda orgs

• Gather context and review changes
• Provide feedback

---

The changes are a straightforward umccr → tidywf org rename across documentation, config, and source files. The intent is clear and the approach is correct. However, there are a few issues worth flagging.

Bug: Missed umccr references in deploy.yaml

Three lines in .github/workflows/deploy.yaml still reference umccr and were not updated. These will cause the CI deployment to upload to the wrong Anaconda org and resolve channels from the old org:

Line 42 — build channel:

rattler-build build \
  --channel umccr \   # ← should be tidywf

Line 52 — upload owner:

rattler-build upload anaconda \
  --owner umccr \   # ← should be tidywf

Lines 58–59 — lock channel args:

CHANNEL_ARGS="--channel umccr --channel conda-forge"
[[ ... ]] && CHANNEL_ARGS="--channel umccr/label/dev ${CHANNEL_ARGS}"
# ↑ both umccr references should be tidywf

The --owner flag on the upload step is the most critical — it controls where the package is published to Anaconda.

Fix this →

Positive: deploy.yaml variable syntax improvement

The PR also switches from bash-style ${VAR} to GitHub Actions expression syntax ${{ env.VAR }} for workflow env vars — a good style improvement for clarity and consistency, even if both forms work in this context.

Everything else looks good

All other files (DESCRIPTION, README.qmd, conda recipes, env YAMLs, docs, vignettes, R/utils.R) have been correctly updated. The changes are mechanical and consistent.

---

Summary: LGTM with one fix needed — the three missed umccr references in deploy.yaml (lines 42, 52, 58–59) must be updated to tidywf before merging, otherwise CI will fail to upload the conda package to the correct org.