Correction of broken links in README #150
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hdamker
added
bug
hdamker
requested review from
bigludo7 and
fernandopradocabrillo
as code owners
|
@bigludo7 @fernandopradocabrillo would be great if you could take care of this PR asap. cc: @tanjadegroot |
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports MegaLinter is graciously provided by |
fernandopradocabrillo
approved these changes
Sep 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Add one of the following kinds:
Correction
What this PR does / why we need it:
The links to the SimSwap YAML where still to sim_swap.yaml and there broken.
Which issue(s) this PR fixes:
Fixes # na
Special notes for reviewers:
Please note that the links within https://github.com/camaraproject/SimSwap/tree/r1.2/README.md would be still broken after the merge of this PR. Therefore I recommend to move the release tag r1.2 to towards the merge commit of this correction PR (can be done without harm as none of the release assets were touched).