How should i report broken links in Docs? Should I open a ticket? For example in grails-spring-security-core link to CAS is broken.

Yes, you should open an issue (ticket) in the relevant repository, such as grails-core or grails-spring-security, to report broken documentation links. This is the recommended approach for contributing fixes or notifying maintainers about documentation problems, as confirmed in the Grails contribution guide. Would you like more detail on how to file such a ticket or where to find the correct repository? Sources: - Grails contribution guide 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

A message from kapa.ai

Yes, the recommended way to report broken links in the Grails documentation (including grails-spring-security-core) is to open a ticket (issue) in the relevant GitHub repository. This approach is confirmed by discussions in the Grails community, where users have reported broken documentation links by opening GitHub issues, and maintainers have responded and tracked the fixes through those tickets. For example, a user reported a broken documentation link for grails-spring-security-core, and the maintainers addressed it via GitHub issues and pull requests [Link to Documentation is Broken](https://github.com/apache/grails-spring-security/issues/1096). So, for your case with the broken CAS link, you should open a new issue in the appropriate repository (e.g., apache/grails-spring-security) and provide details about the broken link. This helps the maintainers track and resolve documentation problems efficiently.

Hey @Arjang, checking in — did my last message answer your question, or should we dig deeper?

Yes