Skip to content

Update repo URLs from zuchka/ to ding-labs/#2

Merged
zuchka merged 1 commit into
mainfrom
update-urls-ding-labs
May 2, 2026
Merged

Update repo URLs from zuchka/ to ding-labs/#2
zuchka merged 1 commit into
mainfrom
update-urls-ding-labs

Conversation

@zuchka

@zuchka zuchka commented May 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

Cleanup PR identified during the relicense work in #1: README.md, action.yml, and the example workflows still reference github.com/zuchka/ paths from before the org migration. GitHub auto-redirects HTML URLs and most API requests, but the api.github.com/repos/zuchka/ding/releases/latest call in action.yml is functional — it resolves version: latest for the DING binary install. Pointing it at the canonical ding-labs URL avoids any future risk if redirects are tightened.

Changed files

File Change
README.md Cross-links to the DING repo and uses: zuchka/ding-action@v1 snippets
action.yml api.github.com/repos/ding-labs/ding/releases/latest + releases/download/... URLs
examples/pytest-workflow.yml uses: zuchka/ding-action@v1ding-labs
examples/ml-training-workflow.yml Same

The author: 'zuchka' line in action.yml stays — that field names the GitHub Actions marketplace publisher (a person), not the org.

Backwards compatibility

Any user currently invoking uses: zuchka/ding-action@vN in their workflows continues to work via GitHub's repo-rename redirect. They should update to ding-labs/ding-action@vN at their convenience but nothing breaks immediately. Worth posting a brief note in release notes for the next tag.

Relationship to #1

Independent of the relicense PR (#1), based off main. Touches different lines in README.md (relicense touches L132, this PR touches L3, L10, L83, L136), so they should rebase cleanly regardless of merge order.

Test plan

  • Visual review of the rendered README on the branch.
  • After merge: tag a new release and use the action in a real workflow to confirm the version: latest API call resolves correctly against ding-labs/ding.

🤖 Generated with Claude Code

The repo migrated to the ding-labs org server-side, but several files
still reference github.com/zuchka/ paths. GitHub auto-redirects HTML
URLs and most API requests, but relying on the redirect is fragile —
especially for the api.github.com call in action.yml that powers
"version: latest" resolution.

Updated:
- README.md: cross-links to the DING repo + uses: lines
- action.yml: api.github.com/repos/ call and releases/download URLs
  for resolving and fetching the DING binary
- examples/pytest-workflow.yml: uses: zuchka/ding-action@v1
- examples/ml-training-workflow.yml: same

The "author: 'zuchka'" line in action.yml stays — that field is the
GitHub Actions marketplace publisher attribution, naming the person.

Note: any user currently invoking "uses: zuchka/ding-action@vN" will
continue to work via GitHub's repo-rename redirect, but they should
update to "uses: ding-labs/ding-action@vN" at their convenience.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@zuchka zuchka merged commit 022dbbc into main May 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant