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

[Feature Request] Add an action to mark a puzzle as duplicate

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rails, ruby

Research direction

Start with the existing cloning filter and puzzle UI, then trace how puzzle attributes are stored and filtered. Define the duplicate column and the UI action or popup for entering another puzzle ID, and verify that filtering hides only the puzzle marked as duplicated while leaving its original visible.

Written by the indexing model from the issue text.

Description

We have some puzzles that are kinda duplicated (similar content but for the same method). These are from before "cloning" was a feature.

We have the filter to hide cloned puzzles but then some puzzles are similar to others but not hidden, and we can end up sharing really similar puzzles too close to each other.

It would be great to have an option to mark a puzzle as a duplicate of another puzzle, so we can filter them out too when looking for things to clone to avoid this.

The idea would be to have a new "duplicated" or "duplicated_puzzle_id" column and a way to mark a puzzle as a duplicate of another puzzle (I imagine the button in the UI opens a popup to input the id of the other puzzle), and then have a new filter to hide duplicated puzzles.

This should only be done on one of the puzzles when there's a duplication, so one does not get hidden when filtering things out.

Dominant language
Ruby
Stars
5
Forks
0
PR merge metrics
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 fastruby/ruby_or_rails

All issues in fastruby/ruby_or_rails

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.