change haxeflixel.com url prefix from www. to https:// for better terminal clicking#83
Merged
ninjamuffin99 merged 1 commit intoHaxeFlixel:devfrom Mar 16, 2025
Merged
Conversation
Member
|
looks fine, I assume you'll merge. do you know whats up with CI? Oh, NVM. I can update the action |
Member
|
if you don't have merge rights on tools, lmk, and you specifically want approval on any changes here, also lmk |
… cli clicking
ninjamuffin99
force-pushed
the
https-click
branch
from
788ab3d to
a4c195a
Compare
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
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.
Many modern terminals automatically highlight and allow links to be clicked. In my small testing (aka just testing with Wezterm and VSCode) seems like as long as it has
https://as it's prefix, it will detect it's a link and allow the link to be clicked easilyin this PR i didnt include the run.n since it will probably create merge conflicts with the other PR i just made hehe... so if/when both of these PRs get merged it will require the run.n to be made!