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

Exercises to add

Closed
  • Is something wrong?
#28 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
content

Research direction

Start by reviewing the unchecked exercises in the Wish list and comparing them with the checked PRed / Merged list. Choose an exercise only after confirming it is not already represented; done means the exercise has been ported and moved from the wish list to the completed list.

Written by the indexing model from the issue text.

Description

@pfertyk, I think we could use a central list of exercises we intend to port in the near future. We can expand this list as needed and check off things as PRs are made.

I think as we check off these exercises, we should move them to the bottom of the list so the exercises left to port are at the top. Feel free to make any edits to this list. I've added a few that'd be easy to port. It's okay if we have more than 20 exercises by the time we launch (Pyret has 48 at the moment, Haxe 69), but I wouldn't hold up the launch just to add more exercises. We can port exercises after the launch too.

Wish list

  • knapsack
  • rational-numbers
  • ledger
  • complex-numbers
  • grep
  • markdown
  • food-chain
  • rail-fence-cipher
  • tournament
  • killer-sudoku-helper

PRed / Merged

  • allergies
  • atbash-cipher
  • binary-search
  • darts
  • flatten-array
  • hello-world
  • isogram
  • leap
  • luhn
  • pangram
  • pop-count
  • raindrops
  • resistor-color
  • resistor-color-duo
  • reverse-string
  • robot-simulator
  • scale-generator
  • space-age
  • spiral-matrix
  • triangle
  • two-fer
Dominant language
GDScript
Stars
8
Forks
10
Avg merge
35m
Merged PRs (30d)
46

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 exercism/gdscript

All issues in exercism/gdscript

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.