Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Clarify check renaming and streamline the publishing workflow

Open
  • Is something wrong?
#523 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
java
Domain
design, frontend

Research direction

Start by tracing the existing check-renaming and publishing workflow and documenting where the UI shows the current publication state. Resolve whether automatic publishing, a prompt, or clearer separate publishing guidance best meets the stated outcome, then define acceptance criteria showing that users understand whether a rename is live and whether further action is required.

Written by the indexing model from the issue text.

Description

Problem

Renaming a check currently requires a separate republish step. New users may reasonably expect the rename to take effect without realizing that they must also publish a new version.

This raises a broader usability question: is the requirement to publish checks clear, and can that workflow be streamlined?

Questions to resolve

  • Should renaming a check automatically publish a new version?
  • Should the user be prompted to choose what to do after renaming?
  • If publishing remains a separate step, how should the UI make that requirement and the current publication state obvious?
  • Can check publishing generally be streamlined or better explained for new users?

Desired outcome

Define and implement a clear rename/publishing experience so users understand whether their rename has taken effect and whether another action is needed. Automatic publishing and prompting are options to evaluate, rather than decisions already made.

Dominant language
Java
Stars
16
Forks
5
Avg merge
14h 45m
Merged PRs (30d)
25

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a 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 CodeForPhilly/benefit-decision-toolkit

All issues in CodeForPhilly/benefit-decision-toolkit

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.