This repository has been archived by the owner on Feb 23, 2024. It is now read-only.
Correct broken *.md links #7108
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
nielslange
added
the
skip-changelog
rubikuserbot
requested review from
a team and
tarunvijwani
and removed request for
a team
nielslange
added
the
focus: documentation
|
The release ZIP for this PR is accessible via: |
|
Size Change: 0 B Total Size: 875 kB ℹ️ View Unchanged
|
|
Merging this directly, as I tested it locally multiple times. |
senadir
pushed a commit
to senadir/woocommerce-blocks
that referenced
this pull request
Nov 12, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
During the porter rotation, I noticed that various links of our *.md files were broken. This PR aims to correct the majority of the broken links. Some links could not be fixed due to technical reasons.
Testing
User Facing Testing
./docs/contributorsfolder by running the command from step 3 in that folder, e.g../docs/designersfolder by running the command from step 3 in that folder../docs/examplesfolder by running the command from step 3 in that folder../docs/internal-developersfolder by running the command from step 3 in that folder../docs/third-party-developersfolder by running the command from step 3 in that folder.Testing steps 4 till 8 are optional and have been mentioned in case a certain folder should be checked individually.