Give tool a better name

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
10/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

The issue provides no files, tests, or entry points. Start by inspecting the repository to identify where the CLI name is defined and which user-facing references use it; done means an agreed replacement name is applied consistently.

Written by the indexing model from the issue text.

Description

This one is pretty boring.

Dominant language
Go
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 azavea/github-labeller

All issues in azavea/github-labeller

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.