jsvine / jsvine/data-tactics

Make tactic names more consistent

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

Nobody has claimed this yet.

Dominant language
No language data
Stars
12
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Right now, there's an awkward mix of imperatives and nouns...

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.

Research direction

No files, tests, or entry points are identified in the issue. Review the tactic definitions and determine a single naming convention for imperatives versus nouns; done means the tactic names consistently follow that convention.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.