Change kit required field to yes/no/blank

Open
  • Is something wrong?
#81 0 comments 0 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
html
Domain
frontend

Research direction

The issue does not name a file or test. Find the change-kit field in the project and read how its current required/default behavior is defined; make it require an explicit yes, no, or blank answer so the question is not missed. Confirm the field presents those choices and does not silently default to an answer.

Written by the indexing model from the issue text.

Description

During scoping it's helpful to force the question to ensure it's not missed. It should be explicitly answered rather than by default

Dominant language
HTML
Stars
6
Forks
4
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 brainthee/CHAOTICA

All issues in brainthee/CHAOTICA

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.