Update DOI, ORCID and Twitter links to use HTTPS #30
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
Author
|
Hello @ourresearch, could you please have a look and consider merging this contribution? |
Contributor
|
Hi! This isn't easy for us to do at the moment unfortunately because the tool build process has become stale, and we don't want to pull code in that we can't push to production. Sorry about that! |
Contributor
|
We're hoping to get more grant funding for the project soon and revitalize it. Fingers crossed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
DOI, ORCID and Twitter all support HTTPS by default, but it helps users' security when they can follow links to the secure websites directly instead of having to be redirected.