Main repo stays clean
Requests are stored as issues in a separate feedback repo instead of mixing product feedback into the source repository.
Destination
Feedback is stored in one dedicated repo
All feedback from this page is routed into the Docs Foundry feedback flow backed by Cloud2BR/docs-foundry-feedback. That keeps product requests separate from the main source repository and avoids any code-branch or pull-request disruption when people submit feedback.
Configured destination
Feedback repo: https://github.com/Cloud2BR/docs-foundry-feedback/issues
Delivery mode: GitHub-native intake. Send feedback opens a prefilled issue in the feedback repo, and that repo processes it with an issues.opened GitHub Actions workflow.
Submit feedback
What do you want to add or improve?
Fill out the request here in the GitHub Pages UI. Send feedback opens a prefilled issue in the feedback repo, and that repo runs its GitHub Actions intake workflow as soon as the issue is submitted.
Why this flow
What this setup solves
No source-repo conflicts
Submissions create records in the feedback flow only, so they do not create commits, branches, or pull requests in the main Docs Foundry repository.
Easy to review later
You can triage, label, close, or convert requests into roadmap items without cluttering the engineering branch history.