Skip to content

fix(cli): fix patched workflow files and examples#6

Merged
sphamjoli merged 4 commits intomainfrom
spha/workflow
Feb 10, 2026
Merged

fix(cli): fix patched workflow files and examples#6
sphamjoli merged 4 commits intomainfrom
spha/workflow

Conversation

@sphamjoli
Copy link
Member

@sphamjoli sphamjoli commented Feb 10, 2026

Description

This PR fixes a patch we needed during the previous PR where we hardcoded the cli to use a version which was built for the PR and not the latest. We also introduce new workflow examples

Type

  • Bug fix
  • Feature
  • Breaking change
  • Documentation
  • Chore

Package

  • @dotns/cli
  • Root/monorepo
  • Documentation

Related Issues

Fixes

  • Workflow files to point to latest artifact.
  • Cleanup workflow files
  • Add workflow that transfers all issues to dotns the core repo
  • Add new workflow examples
  • Bump version to 0.2.0 for CLI

Code

  • Follows project style
  • bun run lint passes
  • bun run format passes
  • bun run typecheck passes

Documentation

  • README updated if needed
  • Types updated if needed

Breaking Changes

  • No breaking changes
  • Breaking changes documented below

Breaking changes:

Testing

None

@github-actions
Copy link

github-actions bot commented Feb 10, 2026

CI Summary

Check Result
Lint Passed
Format Passed
Typecheck Passed
Build Passed
Release Passed
Deploy Example Passed
PR Title Passed
Labels Passed

Release - Passed

Test this PR

Download artifact (GitHub CLI required):

gh run download 21878389335 -n cli-preview-0.0.0-pr.6 -R paritytech/dotns-sdk

Install globally:

Package Manager Command
npm npm install -g ./dotns-cli-0.0.0-pr.6.tgz
yarn yarn global add ./dotns-cli-0.0.0-pr.6.tgz
bun (macOS/Linux) bun add -g "$(pwd)/dotns-cli-0.0.0-pr.6.tgz"
bun (Windows) bun add -g "$PWD\dotns-cli-0.0.0-pr.6.tgz"

Verify:

dotns --help
Deploy Example — Passed
Stage Status
✓ Site validation Site validated
✓ Deploy Deployed (cached)
Property Value
Domain pr6.dotns-example-site.dot
CID bafybeiaewn3tszlqtza4glxqud5ej7tbxht375o5vpz4lhjpi77ruigsna (cached)
URL https://pr6.dotns-example-site.paseo.li

View run

Labels

pkg: cli, dependencies

@sphamjoli sphamjoli changed the title fix(cli): fix patched workflow fix(cli): fix patched workflow files and examples Feb 10, 2026
if [[ -n "$CLI_ARTIFACT" ]]; then
npm install -g ./cli-artifact/dotns-cli-*.tgz
else
gh release download "$CLI_VERSION" -p "*.tgz" -R "$GITHUB_REPOSITORY"
Copy link
Collaborator

Choose a reason for hiding this comment

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

This seems fine but why was "$GITHUB_REPOSITORY" problematic?

Copy link
Collaborator

Choose a reason for hiding this comment

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

nvm this makes sense as $GITHUB_REPOSITORY will be for the local github repo, which may not be this one.

Copy link
Member Author

Choose a reason for hiding this comment

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

deploy.yml is a reusable workflow, when mark3t (the team im helping deploy to bulletin) calls it, $GITHUB_REPOSITORY resolves to the caller's repo (paritytech/mark3t), not paritytech/dotns-sdk. So gh release download would look for the CLI .tgz on the wrong repo and fail. Hardcoding ensures it always pulls from the right place regardless of who calls the workflow.

- name: Transfer to dotns
run: gh issue transfer "$ISSUE_URL" paritytech/dotns
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Claude tells me

The workflow uses secrets.GITHUB_TOKEN to transfer issues to paritytech/dotns, but the default GITHUB_TOKEN is scoped to the current repository only. Cross-repo operations like gh issue transfer to a different repo typically require a PAT with broader permissions. This workflow will likely fail at runtime with a 403.

But I suppose we will find out if and how it fails. What was your vission with the transfer to dotns step here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Your right i was trying to see if it would work but we can change or remove it i was trying to make it that all issues created are transferred to the dotns repo instead of having issues scattered

Copy link
Collaborator

@andrew-ifrita andrew-ifrita left a comment

Choose a reason for hiding this comment

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

LGTM

@sphamjoli sphamjoli merged commit 685ce6f into main Feb 10, 2026
11 checks passed
@sphamjoli sphamjoli deleted the spha/workflow branch February 19, 2026 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants