8000 wiki: add Coddy to Learn page by ntnlbar · Pull Request #106 · golang/wiki · GitHub
[go: up one dir, main page]
Skip to content

wiki: add Coddy to Learn page - #106

Open
ntnlbar wants to merge 1 commit into
golang:masterfrom
ntnlbar:patch-1
Open

wiki: add Coddy to Learn page#106
ntnlbar wants to merge 1 commit into
golang:masterfrom
ntnlbar:patch-1

Conversation

@ntnlbar
@ntnlbar ntnlbar commented Sep 8, 2026
Copy link
Copy Markdown

Adds Coddy's interactive Go course to the Learn page, alongside the other
browser-based exercise platforms already listed (Boot.dev, Exercism,
Codecademy).

The course is free to use and covers the language through generics and
concurrency. Code is compiled and checked server-side, so no local
toolchain is required.

Disclosure: I work on Coddy. Happy to adjust the wording or drop this if
it isn't a fit for the page.

https://coddy.tech/landing/go

@gopherbot
gopherbot commented Sep 8, 2026
Copy link
Copy Markdown

This PR (HEAD: 0cf0ab2) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/wiki/+/829104.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

@gopherbot
gopherbot commented Sep 8, 2026
Copy link
Copy Markdown

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

Please don’t reply on this GitHub thread. Visit golang.org/cl/829104.
After addressing review feedback, remember to publish your drafts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ntnlbar @gopherbot
0