Fix #1131: Document homepage active link pitfall #1174
Merged
Conversation
This file contains hidden or 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
anikethsaha
requested changes
May 14, 2020
There was a problem hiding this comment.
can you change your commit message formatting.
use this guideline
to change the message, use amend,
git commit --amendand after changing the commit message do a force push
anikethsaha
approved these changes
May 15, 2020
|
thanks |
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.
Summary
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx], where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
The first place I went to when noticing this issue was the documentation for the homepage. So that's where I thought it was best to document it.
I'm not a big fan of documenting pitfalls this way though. The list tends to grow with everyone's reports, which are often tied to a very specific use case.
With that being said, I feel like this issue is likely to affect a lot of users but I am new to docsify so I can be totally wrong.
I would be happy to have your opinion and it's fine by me if this PR is rejected.
libdirectory.Closes #1131