Conversation
|
I don't understand why the checks have failed. |
|
Suggestion: If you intend for this pull request to resolve the associated issue and would like for it to be linked to the issue automatically, you can put |
|
I recommend using a commit title that survives on itself, without requiring to access external resources such as sites. Example: |
Update release notes and schedule links from PR QubesOS/qubes-doc#1504 to the latest branch. Fixes: QubesOS/qubes-issues#10428
739f042 to
b5afd2e
Compare
|
Sorry for the mess. |
I believe it's for current 4.2 users who want to upgrade to 4.3.
Not at all! Thank you for contributing! |
I don't see that link in the list:
|
|
Interesting, while the yaml page has list of title + URL, the html version ( IMO it should just use |
After another discussion (QubesOS#273), I did the following: * update some links from the download page, that were pointing to documentation URLs on www.qubes-os.org instead of doc.qubes-os.org * remove the filtering of the download links based on their name, allowing "Upgrading to Qubes R[...]" links to be displayed * remove duplicate title attribute on links, because I don't think it is good for accessibility
|
Thanks for the tip ! |
|
That looks like a more general future proof solution.
|
|
Should I close this PR? |
Update release notes and schedule links from PR QubesOS/qubes-doc#1504
to the latest branch.
Note: I don't understand the purpose of the "Upgrading to Qubes R4.3" link.
Fixes: QubesOS/qubes-issues#10428