-
-
Notifications
You must be signed in to change notification settings - Fork 103
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: dispatch/reboot
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: dispatch/reboot
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.0.x
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 13 commits
- 6 files changed
- 3 contributors
Commits on Oct 20, 2018
-
Configuration menu - View commit details
-
Copy full SHA for f575941 - Browse repository at this point
Copy the full SHA f575941View commit details
Commits on Nov 4, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 016ddea - Browse repository at this point
Copy the full SHA 016ddeaView commit details -
Merge pull request #207 from dispatch/1.0/realm-with-scheme
[1.0] Allow to set scheme in as keyword
Configuration menu - View commit details
-
Copy full SHA for 6687f2a - Browse repository at this point
Copy the full SHA 6687f2aView commit details -
Configuration menu - View commit details
-
Copy full SHA for fcff70d - Browse repository at this point
Copy the full SHA fcff70dView commit details -
Configuration menu - View commit details
-
Copy full SHA for c78caf0 - Browse repository at this point
Copy the full SHA c78caf0View commit details
Commits on Oct 5, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 802eac1 - Browse repository at this point
Copy the full SHA 802eac1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1461932 - Browse repository at this point
Copy the full SHA 1461932View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0e4eb5d - Browse repository at this point
Copy the full SHA 0e4eb5dView commit details
Commits on Dec 27, 2019
-
Correctly url encode emoji in path segments
The previous implementation borked on emoji because invoking char.toString on a single UTF-8 part of a larger UTF-16 pair results in the encoding presenting "?" as the value. This implementation works primarily on Bytes and avoids having to invoke char.toString and therefore is capable of correctly encoding emoji characters into a UTF-8 url encoded path segment. This did involve re-working some of the valid character detection for path segments, so there is likely a delta to the overall performance, but I think it should be negligible.
Configuration menu - View commit details
-
Copy full SHA for a3e46a2 - Browse repository at this point
Copy the full SHA a3e46a2View commit details -
Configuration menu - View commit details
-
Copy full SHA for c62507e - Browse repository at this point
Copy the full SHA c62507eView commit details -
Merge pull request #227 from dispatch/1.0/encode-emoji
[1.0.x] Correctly url encode emoji in path segments
Configuration menu - View commit details
-
Copy full SHA for 58e4344 - Browse repository at this point
Copy the full SHA 58e4344View commit details -
Configuration menu - View commit details
-
Copy full SHA for b43e103 - Browse repository at this point
Copy the full SHA b43e103View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5dd068a - Browse repository at this point
Copy the full SHA 5dd068aView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...1.0.x