💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

Hey there! 👋

Thanks for posting in the GitHub Community, @lucdev01234-png ! You are more likely to get a useful response if you are posting in the applicable category. The Actions category is a place for our community to discuss and provide feedback on GitHub Actions, the CI/CD platform that allows you to automate your build, test, and deployment pipeline.

I've gone ahead and moved this to the correct category for you. Good luck!

Here's a workflow that's been effective:

• Check the OpenAPI spec on every pull request.
• Generate documentation automatically during CI, rather than editing it manually.
• Stop the process if the spec is invalid or the docs are outdated.
• Review changes to the OpenAPI file and the implementation together in the same PR.
  For tools, Redocly CLI and Swagger CLI are both good options. They work well with GitHub Actions, letting you validate specs before merging.
  The biggest win for us was ditching manually updated API docs. Once the OpenAPI spec was the single source of truth, keeping docs in sync became much easier because they were generated directly from the spec.