-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken Edit links #3321
Fix broken Edit links #3321
Conversation
include::./packetbeat-geoip.asciidoc[] | ||
|
||
pass::[<?edit_url https://github.com/elastic/beats/edit/master/libbeat/docs/shared-logstash-config.asciidoc ?>] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think here it should point to: https://github.com/elastic/beats/edit/master/packetbeat/docs/shared-logstash-config.asciidoc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, it looks like your link is working: https://github.com/elastic/beats/edit/master/libbeat/docs/shared-logstash-config.asciidoc
…3312, #3331, #3336) (#3345) * Edit haproxy module docs * Add fixes from review feedback * Fix broken Edit links * Clarify when registry file is updated in docs (#3274) See #3220 (comment) * Update close_timeout docs (#3320) Clarified close_timeout when there are updates to the file. * Fix typo in regexp Should be `regexp` and not `reqexp` * Fix a couple of typos and a broken link * Change "versions" to "supported_protocols" (#3336) Urso pointed out during the Heartbeat review that this name is wrong.
…3331, #3336) (#3347) * Edit haproxy module docs * Add fixes from review feedback * Fix broken Edit links * Update close_timeout docs (#3320) Clarified close_timeout when there are updates to the file. * Fix typo in regexp Should be `regexp` and not `reqexp` * Fix a couple of typos and a broken link * Change "versions" to "supported_protocols" (#3336) Urso pointed out during the Heartbeat review that this name is wrong.
…lastic#3320, elastic#3312, elastic#3331, elastic#3336) (elastic#3347) * Edit haproxy module docs * Add fixes from review feedback * Fix broken Edit links * Update close_timeout docs (elastic#3320) Clarified close_timeout when there are updates to the file. * Fix typo in regexp Should be `regexp` and not `reqexp` * Fix a couple of typos and a broken link * Change "versions" to "supported_protocols" (elastic#3336) Urso pointed out during the Heartbeat review that this name is wrong.
…lastic#3274, elastic#3320, elastic#3312, elastic#3331, elastic#3336) (elastic#3345) * Edit haproxy module docs * Add fixes from review feedback * Fix broken Edit links * Clarify when registry file is updated in docs (elastic#3274) See elastic#3220 (comment) * Update close_timeout docs (elastic#3320) Clarified close_timeout when there are updates to the file. * Fix typo in regexp Should be `regexp` and not `reqexp` * Fix a couple of typos and a broken link * Change "versions" to "supported_protocols" (elastic#3336) Urso pointed out during the Heartbeat review that this name is wrong.
This PR fixes the broken Edit links that pointed to shared (single-sourced) content in libbeat.
Because the macro that we use to set the Edit url doesn't accept variables in the path (couldn't use
{doc-branch}
), I decided to point edits tomaster
rather than a specific branch name. This in keeping with our preference for having PRs submitted to themaster
branch and then back/forward ported. It's also consistent with how Logstash handles doc edits.All the Edit links in the book will now point to the
master
branch. The one main drawback of this approach is that the user might see a problem that exists in the current doc, but has been fixed inmaster
. Also, the content inmaster
won't always match what the user sees in the published doc (especially as the doc ages), and it's possible that the link will no longer work if we delete the file inmaster
.It's the best solution we have for now, though, unless we want to update all the URL paths in all these links whenever we cut a new branch.
NOTE: You'll probably notice that there area couple of instances where I set the Edit url to the location of the shared logstash config doc even though there is a corresponding local file. The local file is just a heading that wraps the shared content, so I figured it was better just to point users to the shared content.