-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
fix #835 :Link target of repo's GitHub Corner add new independent config cornerExternalLinkTarget
.
#842
Conversation
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.
Thanks for the PR and sorry for the delay.
Left some suggestion.
you need to update the docs as well with this . |
Update the docs and squash the commits and then we are good to merge 👍 |
rm CNAME add CNAME add repo test back to the origin index.html fix: the Git corner displayed bigger when the externalLinkTarget = '' [update] a new independent config for corner link target attribute. [update doc] add the `cornerExternalLinkTarget` config in the doc.
@anikethsaha I updated the docs and squashed the commits.Is there anything else I need to do? |
cornerExternalLinkTarget
.
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.
Good work 🎉
fixes #843
Summary
Link target of repo's GitHub Corner opens repo in current window/tab.
Fix : Link target of repo's GitHub Corner according to externalLinkTarget config. #835
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:
lib
directory.