This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
DocFit
Docs PRs opened for you when your code merges
DocFit is documentation CI for GitHub. When a code PR merges, it finds the affected documentation, write fixes, verifies it with build, lint and any custom commands, and then opens a docs PR for your team to review. It never merges on its own.
DocFit is a GitHub App for one job: keeping API documentation in sync with the code that just merged.
For past 6 years I have worked a lot on the backend writing and modifying API endpoints on daily basis. As an API first company we used to make sure to update our API documents before releasing the changes. In past 2-3 years, with AI now writing the code, we are merging way more changes than our engineers could maintain docs for.
The problem is familiar to anyone who maintains API docs, public or private. A pull request merges, the code is correct, and a docs page is now wrong. Often it isn't the headline change. In our public example, a PR titled "filter refunds by reason" also lowered the maximum page size from 100 to 50, and the docs page never listed the limit at all. Nobody reviewing the code saw the docs page; nobody owning the docs saw the code PR.
What DocFit does on every merge:
1. Decides whether docs could be affected. If not, it leaves a "No docs impact" comment and stops. 2. Reads the whole change: diff, commits, review comments and the linked Jira or GitHub issue. 3. Finds affected pages or if any new documentations are required. 4. Fixes the documentation in your documentation framework's format. 5. Checks it: your docs build and linters, links, OpenAPI lint, and any custom commands. 6. Opens a docs PR for your team and notifies you over Slack. DocFit never merges.
Works with Mintlify, Docusaurus, Redocly/OpenAPI, MkDocs, Nextra, VitePress and plain Markdown, in the same repo or a separate docs repo.
Free for public repos and one private repo. During setup you can dry-run it on your last 5 merges and see what it would have changed.
We'll be providing extended free trial for Team plan in exchange for honest feedback on the docs PRs. Reply here or email contact@docfit.dev.
I'd love to hear any suggestions or feedback.
About DocFit on Product Hunt
“Docs PRs opened for you when your code merges”
DocFit was submitted on Product Hunt and earned 24 upvotes and 13 comments, placing #39 on the daily leaderboard. DocFit is documentation CI for GitHub. When a code PR merges, it finds the affected documentation, write fixes, verifies it with build, lint and any custom commands, and then opens a docs PR for your team to review. It never merges on its own.
On the analytics side, DocFit competes within Software Engineering, Developer Tools and GitHub — topics that collectively have 607.9k followers on Product Hunt. The dashboard above tracks how DocFit performed against the three products that launched closest to it on the same day.
Who hunted DocFit?
DocFit was hunted by Siddharth Singh. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of DocFit including community comment highlights and product details, visit the product overview.
Hi Product Hunt
DocFit is a GitHub App for one job: keeping API documentation in sync with the code that just merged.
For past 6 years I have worked a lot on the backend writing and modifying API endpoints on daily basis. As an API first company we used to make sure to update our API documents before releasing the changes. In past 2-3 years, with AI now writing the code, we are merging way more changes than our engineers could maintain docs for.
The problem is familiar to anyone who maintains API docs, public or private. A pull request merges, the code is correct, and a docs page is now wrong. Often it isn't the headline change. In our public example, a PR titled "filter refunds by reason" also lowered the maximum page size from 100 to 50, and the docs page never listed the limit at all. Nobody reviewing the code saw the docs page; nobody owning the docs saw the code PR.
What DocFit does on every merge:
1. Decides whether docs could be affected. If not, it leaves a "No docs impact" comment and stops.
2. Reads the whole change: diff, commits, review comments and the linked Jira or GitHub issue.
3. Finds affected pages or if any new documentations are required.
4. Fixes the documentation in your documentation framework's format.
5. Checks it: your docs build and linters, links, OpenAPI lint, and any custom commands.
6. Opens a docs PR for your team and notifies you over Slack. DocFit never merges.
Works with Mintlify, Docusaurus, Redocly/OpenAPI, MkDocs, Nextra, VitePress and plain Markdown, in the same repo or a separate docs repo.
See real output without signing up:
- the code PR: https://github.com/Docfit/exampl...
- the docs PR DocFit opened: https://github.com/Docfit/exampl...
Free for public repos and one private repo. During setup you can dry-run it on your last 5 merges and see what it would have changed.
We'll be providing extended free trial for Team plan in exchange for honest feedback on the docs PRs. Reply here or email contact@docfit.dev.
I'd love to hear any suggestions or feedback.