Skip to content

chore: update repo references after rename to bruno-cli-action#3

Merged
bijin-bruno merged 1 commit into
usebruno:mainfrom
sundram-bruno:chore/repo-rename-bruno-cli-action
Jun 9, 2026
Merged

chore: update repo references after rename to bruno-cli-action#3
bijin-bruno merged 1 commit into
usebruno:mainfrom
sundram-bruno:chore/repo-rename-bruno-cli-action

Conversation

@sundram-bruno

Copy link
Copy Markdown
Contributor

Sweeps the codebase for the old bruno-run-action name and updates references to bruno-cli-action.

GitHub auto-redirects the old name on uses: and Git URLs, so nothing functionally broke — this is hygiene so README quickstarts and recipes point at the canonical new repo path going forward.

Changes

  • README.md — all uses: usebruno/bruno-run-action@v1 snippets across quickstart and the 13 recipes updated to usebruno/bruno-cli-action@v1.
  • package.json — action's internal npm package name renamed (private package, not published to npm).
  • package-lock.json — regenerated.
  • tests/collection/bruno.json — fixture collection name updated for consistency.

Ref: BRU-3280

The repo was renamed from `usebruno/bruno-run-action` to `usebruno/bruno-cli-action`. Sweeping the codebase for old refs and updating them. GitHub auto-redirects the old name on `uses:` and Git URLs, so this is hygiene rather than a functional fix.

- README: all `uses: usebruno/bruno-run-action@v1` quickstart and recipes updated to the new name.
- package.json: action's npm package name renamed (private package, not published).
- package-lock.json: regenerated to reflect the new name.
- tests/collection/bruno.json: fixture collection name updated for consistency.
@sundram-bruno sundram-bruno force-pushed the chore/repo-rename-bruno-cli-action branch from 039305e to 048486d Compare June 9, 2026 12:31
@bijin-bruno bijin-bruno merged commit ff2fda5 into usebruno:main Jun 9, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants