HI Team,
Our production-level API documentation site is live and actively being used by our customers. Due to this, we are strictly avoiding making any direct changes in the main/production branch, as even a small issue can cause our live documentation to break — which has a serious impact on our users.
We are trying to follow a proper release workflow involving three branches:
dev — for initial Swagger imports and development/testing
staging — for internal review after dev
prod — for final deployment
Unfortunately, while Apidog does support branching, I am currently only able to import Swagger files directly into the main branch. I am unable to import Swagger documentation into the dev branch, which is breaking our intended safe deployment workflow.
Our Requirement:
We need the ability to:
Import Swagger files into non-main branches, particularly dev.
Review and test in dev, then promote to staging, and finally to prod.
Why This Is Urgent:
Our live documentation is exposed to customers. If a mistake occurs during direct imports or edits in the main branch, it can break the live site instantly. This has already caused downtime several times, and we want to avoid any recurrence by following a proper dev-to-prod process.
Kindly prioritize this request as this is very urgent now