Allow using `fly` instead of only `flyctl`

Open
  • Is something wrong?
#44 4 comments 13 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, typescript
Domain
ci-cd, devops

Research direction

Start by tracing how this GitHub Action resolves and invokes the flyctl command in workflows, then compare that behavior with the official documentation examples using fly. Confirm the change by running or adding a workflow check showing that fly is accepted wherever flyctl is currently required.

Written by the indexing model from the issue text.

Description

Hi!

I just had a problem where I got fly: command not found. When I changed to flyctl it started working.

In your official documentation you use fly instead of flyctl quite a lot. I would therefore recommend that using fly would also be OK in workflows using this action. I think it should be consistent with the normal installation (which adds the symlink fly->flyctl).

Dominant language
TypeScript
Stars
311
Forks
38
Avg merge
1d 6h
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from superfly/flyctl-actions

All issues in superfly/flyctl-actions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.