-
Notifications
You must be signed in to change notification settings - Fork 126
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
Fixing broken links described in issue#2701 #2702
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2702 +/- ##
==========================================
+ Coverage 91.33% 91.35% +0.01%
==========================================
Files 309 309
Lines 60380 60380
==========================================
+ Hits 55151 55160 +9
+ Misses 5229 5220 -9
Flags with carried forward coverage won't be shown. Click here to find out more. see 5 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Signed-off-by: devskillz47 <[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.
Can we link this to edge instead of 0.12:
- edge will not go out of date as a long
- edge effects what is directly in github so it is the more correct link I think
will do, but took a little break for the holidays... :p |
All good, I just wanted to track it before I forget :) |
Np. :p
…On Tue, 7 Jan 2025, 15:26 Heinz N. Gies, ***@***.***> wrote:
All good, I just wanted to track it before I forget :)
—
Reply to this email directly, view it on GitHub
<#2702 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOAGJAXE6VBGMIWQ475JBV32JPIZZAVCNFSM6AAAAABUASY542VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZVGI4TINRQG4>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Np. :p |
so, i had a more in depth look at this. it seems that currently everything points to v0.12. my only concern in moving it to edge would be that if in the installation instructions we point to the latest release (in this case v0.12) and in the documentation we point it to edge the features described in the documentation might not be there for the users who followed the instructions which could be quite cumbersome. |
Pull request
Fix "broken" links included in the Issue#2701(#2701)