-
Notifications
You must be signed in to change notification settings - Fork 170
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
[chore] Fix references to plugin/storage
#840
[chore] Fix references to plugin/storage
#840
Conversation
Signed-off-by: Mahad Zaryab <[email protected]>
✅ Deploy Preview for romantic-neumann-1959d7 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Mahad Zaryab <[email protected]>
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.
Technically all other links are broken too, for older docs. This wasn't a great practice to link to main
branch. GitHub allows referring to tags, this would be a better approach, e.g. https://github.com/jaegertracing/jaeger/tree/v1.66.0/internal/storage/v1/grpc
We have two options here
- Fix the release script that copies next-release files into a numbered release and perform substitution of
/main/
for the concrete version being released. This will ensure stable links, but thenext-release
files will always be slightly different. - Use the versions where the file first appeared, e.g. https://github.com/jaegertracing/jaeger/tree/v1.20.0/plugin/storage/grpc still works today.
I think option 1 is better because it allows testing of the next-release
files without having a versioned release (i.e. still pointing to the latest main). And we could script a codemod for old versions by changing the links to the respective versions.
We do have a link validation script for external links, it's just a PITA to run and it's too flaky to be run via CI
## Which problem is this PR solving? - Addresses #840 (review) ## Description of the changes - Wrote a short script and ran it to replace all instances of `https://github.com/jaegertracing/jaeger/tree/main` with `https://github.com/jaegertracing/jaeger/tree/{version}` so that documentation links never go stale. ## How was this change tested? - Manually checked the links to ensure they are reachable ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits Signed-off-by: Mahad Zaryab <[email protected]>
…ion (#841) ## Which problem is this PR solving? - Addresses #840 (review) ## Description of the changes - Added a step to the release script to replace all instances of `https://github.com/jaegertracing/jaeger/tree/main` in `next-release/` and `next-release-v2/` with `https://github.com/jaegertracing/jaeger/tree/{version}` ## How was this change tested? - Ran the same sed command when performing the backfill in #842 ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits --------- Signed-off-by: Mahad Zaryab <[email protected]>
Which problem is this PR solving?
Description of the changes
plugin/storage
tointernal/storage/v1
Checklist