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

Mentored coding

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

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start with the mentored coding guide linked in the issue, then use the #cyf-mentored-coding scheduling canvas or post in the channel if no times are available. Done means completing a session with a mentor, bringing a problem, explaining the thought process, planning and writing the code, and checking that it works.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 1 📅 Sprint 2 📅 Sprint 3 Module-Data-Groups Recurring Submit:None

Every week you should have a mentored coding session. This is an opportunity for you to work on a problem with a mentor together, getting support, and practice breaking down and solving problems.

If your region has education team support, you are expected to have a session with the education team every other week. In the other weeks, you should have a session with a volunteer.

You should come to the session with a problem to work on. We recommend a Codewars exercise, but it could be a backlog task, or a project you're working on.

See the mentored coding guide for guidance.

For education team sessions, you should already have a regular time booked. For volunteer sessions, book time with a volunteer using one of the Scheduling links in the #cyf-mentored-coding slack channel's canvas. If there are no available times, please post in #cyf-mentored-coding.

Remember, as a trainee, you will need to explain your thought process, plan out what to do, write the code and check it works.

Dominant language
JavaScript
Stars
1
Forks
327
Avg merge
3d 7h
Merged PRs (30d)
3

Contributor guide

Open the 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 CodeYourFuture/Module-Data-Groups

All issues in CodeYourFuture/Module-Data-Groups

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.