Modern Git Academy is a technical education site, and technical accuracy is the thing it most wants to get right. Corrections are genuinely welcome.
There are two separate routes here, because the questions are different: something you bought, and something we published.
Bought something and need help
Section titled “Bought something and need help”Downloads, re-downloads, updates, receipts and refunds have their own page: order help. It covers the common case — the download page did not open after payment — without needing anyone to reply to you.
Purchases, downloads and refunds: admin@moderngitacademy.com. Include the Stripe receipt and the product name.
Corrections and errors in lessons
Section titled “Corrections and errors in lessons”Email admin@moderngitacademy.com. Please include the page URL and, for technical reports, the details listed below. Corrections to technical content are made to the lesson itself — see the corrections policy for how each class is handled.
What is most useful to report
Section titled “What is most useful to report”Technical errors. A command that does not behave as documented, output that does not match what the lesson shows, or an explanation that is misleading. These take priority over everything else.
To make a report actionable, please include:
- The page URL.
- The command you ran, exactly.
- The output you got, and what the lesson said to expect.
- Your Git version (
git --version) and operating system.
That is usually enough to reproduce and fix an issue without a back-and-forth.
Out-of-date instructions. Installation guides, package manager commands and vendor interfaces age. Lessons that cover them carry a note recording what they were verified against. If a version-sensitive lesson has drifted, saying so is useful.
Explanations that did not land. If a concept is technically correct but genuinely confusing, that is worth reporting too. Explanations that mislead by simplification are a defect, not a stylistic preference.
Content suggestions. Topics you want covered, or gaps in the existing curriculum.
What this site does not offer
Section titled “What this site does not offer”Personal Git support. This is a publication, not a help desk. There is no capacity to debug individual repositories or answer general “how do I do X” questions. (Support for something you bought is different, and is handled: see order help.)
For those, better options exist:
Guest posts, link exchanges and sponsored content. This site does not publish guest articles, exchange links, or accept payment for placement, mentions or links. Such enquiries are not answered.
Paid consulting or training. Not offered.
Before reporting an error
Section titled “Before reporting an error”Two quick checks that resolve most reports:
- Compare your Git version against the one in the lesson’s Verified badge, shown under the title. Behaviour and output wording do change between releases.
- Check your configuration with
git config --list --show-scope --show-origin. A setting in an unexpected scope — particularly a--localone — explains a large share of “this does not work for me” reports. Lesson 4 covers configuration scopes.
If both check out, the lesson is probably wrong and the report is worth making.
Corrections policy
Section titled “Corrections policy”Corrections to technical content are made directly to the lesson concerned, so readers always see accurate material rather than an accurate correction appended to an inaccurate page.
Lessons whose instructions can age carry a Verified badge recording the environment they were last checked against. Where a fix changes the substance of what a lesson teaches, that badge is updated too.