1For the latest version of this document, please see [https://github.com/bos/aeson/blob/master/changelog.md](https://github.com/bos/aeson/blob/master/changelog.md).
7* Adds a parameterized parser `jsonWith` that can be used to choose how to handle duplicate keys in objects, thanks to Xia Li-Yao.
9* Add generic implementations of `FromJSONKey` and `ToJSONKey`, thanks to Xia Li-Yao. Example:
16opts = defaultJSONKeyOptions { keyModifier = toLower }
18instance ToJSONKey Foo where
19 toJSONKey = genericToJSONKey opts
21instance FromJSONKey Foo where
22 fromJSONKey = genericFromJSONKey opts
26* aeson now uses `time-compat` instead of `time-locale-compat`, thanks to Oleg Grenrus.
27* Prepare for `MonadFail` breakages in GHC 8.8, thanks to Oleg Grenrus.
28* Require `bytestring >= 0.10.8.1` for newer GHCs to avoid build failures, thanks to Oleg Grenrus.
29* Support `primitive 0.7.*`, thanks to Adam Bergmark.
30* Allow `semigroups 0.19.*` and `hashable 1.3.*`, thanks to Oleg Grenrus.
31* Fix a typo in the error message when parsing `NonEmpty`, thanks to Colin Woodbury.
32* Document surprising behavior when using `omitNothingFields` with type variables, thanks to Xia Li-Yao.
35* Code cleanup by Oleg Grenrus
36* Fix dependencies of the benchmarks on older GHC's, thanks to Xia Li-Yao.
39* Improve error messages for FromJSON in existing instances and GHC Generic implementation. Thanks to Xia Li-Yao & Igor Pashev.
40* Tweak error-reporting combinators and their documentation. Thanks to Xia Li-Yao.
41 * `typeMismatch` is now about comparing JSON types (i.e., the expected and actual names of the Value constructor).
42 * `withObject` and other `with*` combinators now also mention the JSON types they expect
43 * New `unexpected` and `prependFailure` combinators.
44* Add `Contravariant` `ToJSONKeyFunction` instance. Thanks to Oleg Grenrus.
45* Add `KeyValue` instance for `Object`. Thanks to Robert Hensing.
46* Improve performance when parsing certain large numbers, thanks to Oleg Grenrus.
47* Add `Data.Aeson.QQ.Simple` - A limited version of aeson-qq. Thanks to Oleg Grenrus.
48* Exposes internal helper functions like `<?>`, `JSONPath`, and `parseIndexedJSON` from `Data.Aeson` module. Thanks to Abid Uzair.
49* Better error messages when there are syntax errors parsing objects and arrays. Thanks to Fintan Halpenny.
50* Support building with `th-abstraction-0.3.0.0` or later. Thanks to Ryan Scott.
54* Add `Data.Aeson.QQ.Simple` which is a simpler version of the `aeson-qq` package, it does not support interpolation, thanks to Oleg Grenrus.
55* Add `Contravariant ToJSONKeyFunction` instance, thanks to Oleg Grenrus.
56* Add `KeyValue Object` instance, thanks to Robert Hensing
57* Improved performance when parsing large numbers, thanks to Oleg Grenrus.
61* Optimizations of generics, thanks to Rémy Oudompheng, here are some numbers for GHC 8.4:
62 * Compilation time: G/BigProduct.hs is 25% faster, G/BigRecord.hs is 2x faster.
63 * Runtime performance: BigRecord/toJSON/generic and BigProduct/encode/generic are more than 2x faster.
64* Added To/FromJSON instances for `Void` and Generics's `V1`, thanks to Will Yager
65* Added To/FromJSON instances for `primitive`'s `Array`, `SmallArray`, `PrimArray` and `UnliftedArray`, thanks to Andrew Thad.
66* Fixes handling of `UTCTime` wrt. leap seconds , thanks to Adam Schønemann
67* Warning and documentation fixes thanks to tom-bop, Gabor Greif, Ian Jeffries, and Mateusz Curyło.
71This release introduces bounds on the size of `Scientific` numbers when they are converted to other arbitrary precision types that do not represent them efficiently in memory.
73This means that trying to decode a number such as `1e1000000000` into an `Integer` will now fail instead of using a lot of memory. If you need to represent large numbers you can add a newtype (preferably over `Scientific`) and providing a parser using `withScientific`.
75The following instances are affected by this:
77* `FromJSONKey Natural`
79* `FromJSONKey Integer`
80* `FromJSON NominalDiffTime`
82For the same reasons the following instances & functions have been removed:
83* Remove `FromJSON Data.Attoparsec.Number` instance. Note that `Data.Attoparsec.Number` is deprecated.
84* Remove deprecated `withNumber`, use `withScientific` instead.
86Finally, encoding integral values with large exponents now uses scientific notation, this saves space for large numbers.
90* Catch 0 denominators when parsing Ratio
94* Fix bug in generically derived `FromJSON` instances that are using `unwrapUnaryRecords`, thanks to Xia Li-yao
95* Allow base-compat 0.10.*, thanks to Oleg Grenrus
100* `GKeyValue` has been renamed to `KeyValuePair`, thanks to Xia Li-yao
101* Removed unused `FromJSON` constraint in `withEmbeddedJson`, thanks to Tristan Seligmann
104* Optimizations of TH toEncoding, thanks to Xia Li-yao
105* Optimizations of hex decoding when using the default/pure unescape implementation, thanks to Xia Li-yao
106* Improved error message on `Day` parse failures, thanks to Gershom Bazerman
107* Add `encodeFile` as well as `decodeFile*` variants, thanks to Markus Hauck
108* Documentation fixes, thanks to Lennart Spitzner
109* CPP cleanup, thanks to Ryan Scott
113* Add `Ord` instance for `JSONPathElement`, thanks to Simon Hengel.
118* Added `withEmbeddedJSON` to help parse JSON embedded inside a JSON string, thanks to Jesse Kempf.
119* Memory usage improvements to the default (pure) parser, thanks to Jonathan Paugh. Also thanks to Neil Mitchell & Oleg Grenrus for contributing a benchmark.
120* `omitNothingFields` now works for the `Option` newtype, thanks to Xia Li-yao.
121* Some documentation fixes, thanks to Jonathan Paug & Philippe Crama.
125* Add `FromJSON` and `ToJSON` instances for
126 * `DiffTime`, thanks to Víctor López Juan.
127 * `CTime`, thanks to Daniel Díaz.
128* Fix handling of fractions when parsing Natural, thanks to Yuriy Syrovetskiy.
129* Change text in error messages for Integral types to make them follow the common pattern, thanks to Yuriy Syrovetskiy.
130* Add missing `INCOHERENT` pragma for `RecordToPair`, thanks to Xia Li-yao.
131* Everything related to `Options` is now exported from `Data.Aeson`, thanks to Xia Li-yao.
132* Optimizations to not escape text in clear cases, thanks to Oleg Grenrus.
133* Some documentation fixes, thanks to Phil de Joux & Xia Li-yao.
137* Add `parserThrowError` and `parserCatchError` combinators, thanks to Oleg Grenrus.
139* Add `Generic` instance for `Value`, thanks to Xia Li-yao.
141* Fix a mistake in the 1.2.0.0 changelog, the `cffi` flag is disabled by default! Thanks to dbaynard.
145* `tagSingleConstructors`, an option to encode single-constructor types as tagged sums was added to `Options`. It is disabled by default for backward compatibility.
147* The `cffi` flag is now turned off (`False`) by default, this means C FFI code is no longer used by default. You can flip the flag to get C implementation.
149* The `Options` constructor is no longer exposed to prevent new options from being breaking changes, use `defaultOptions` instead.
151* The contents of `GToJSON` and `GToEncoding` are no longer exposed.
153* Some INLINE pragmas were removed to avoid GHC running out of simplifier ticks.
157* Fix an accidental change in the format of `deriveJSON`. Thanks to Xia Li-yao!
159* Documentation improvements regarding `ToJSON`, `FromJSON`, and `SumEncoding`. Thanks to Xia Li-yao and Lennart Spitzner!
163* Added a pure implementation of the C FFI code, the C FFI code. If you wish to use the pure haskell version set the `cffi` flag to `False`. This should make aeson compile when C isn't available, such as for GHCJS. Thanks to James Parker & Marcin Tolysz!
165* Using the `fast` flag can no longer cause a test case to fail. As far as we know this didn't affect any users of the library itself. Thanks to Xia Li-yao!
169* Added instances for `UUID`.
171* The operators for parsing fields now have named aliases:
172 - `.:` => `parseField`
173 - `.:?` => `parseFieldMaybe`
174 - `.:!` => `parseFieldMaybe'`
175 - These functions now also have variants with explicit parser functions: `explicitParseField`, `explicitParseFieldMaybe`, "explicitParseFieldMaybe'`
176Thanks to Oleg Grenrus.
178* `ToJSONKey (Identity a)` and `FromJSONKey (Identity a)` no longer require the unnecessary `FromJSON a` constraint. Thanks to Oleg Grenrus.
180* Added `Data.Aeson.Encoding.pair'` which is a more general version of `Data.Aeson.Encoding.pair`. Thanks to Andrew Martin.
182* `Day`s BCE are properly encoded and `+` is now a valid prefix for `Day`s CE. Thanks to Matt Parsons.
184* Some commonly used ToJSON instances are now specialized in order to improve compile time. Thanks to Bartosz Nitka.
187[JSONTestSuite](https://github.com/nst/JSONTestSuite) cleanups, all
188motivated by tighter RFC 7159 compliance:
190* The parser now rejects numbers for which
191 [the integer portion contains a leading zero](https://github.com/bos/aeson/commit/3fb7c155f2255482b1b9566ec5c1eaf9895d630e).
192* The parser now rejects numbers for which
193 [a decimal point is not followed by at least one digit](https://github.com/bos/aeson/commit/ecfca35a45286dbe2bbaf5f62354be393bc59b66),
194* The parser now rejects documents that contain [whitespace outside the
195 set {space, newline, carriage return, tab}](https://github.com/bos/aeson/commit/8ef622c2ad8d4a109884e17c2792238a2a320e44).
197Over 90% of JSONTestSuite tests currently pass. The remainder can be
198categorised as follows:
200* The string parser is strict with Unicode compliance where the RFC
201 leaves room for implementation-defined behaviour (tests prefixed
202 with "`i_string_`". (This is necessary because the `text` library
203 cannot accommodate invalid Unicode.)
205* The parser does not (and will not) support UTF-16, UTF-32, or byte
207* The parser accepts unescaped control characters, even though the RFC
208 states that control characters must be escaped. (This may change at
209 some point, but doesn't seem important.)
213* Fixes a regression where a bunch of valid characters caused an
214 "Invalid UTF8-Stream" error when decoding. Thanks to Vladimir
215 Shabanov who investigated and fixed this.
219* Fixes a regression where it was no longer possible to derive
220 instances for types such as `data T a = T { f1 :: a, f2 :: Maybe a
223Thanks to Sean Leather for fixing this, and to Ryan Scott for helping out.
227* Decoding performance has been significantly improved (see
228 https://github.com/bos/aeson/pull/452). Thanks to @winterland1989.
230* Add `ToJSON`/`FromJSON` instances for newtypes from
231 `Data.Semigroup`: `Min`, `Max`, `First`, `Last`, `WrappedMonoid`,
232 `Option`. Thanks to Lennart Spitzner.
234* Make the documentation for `.:!` more accurate. Thanks to Ian Jeffries.
240* Introduced new `FromJSONKey` and `ToJSONKey` type classes that are
241 used to encode maps without going through HashMap. This also allows arbitrary
242 serialization of keys where a string-like key will encode into an object and
243 other keys will encode into an array of key-value tuples.
245* Added higher rank classes: `ToJSON1`, `ToJSON2`, `FromJSON1`, and
248* Added `Data.Aeson.Encoding` with functions to safely write `ToJSON`
249 instances using `toEncoding`.
253* A Cabal `fast` flag was added to disable building with optimizations. This drastically speeds up compiling both aeson ***and*** libraries using aeson so it is recommended to enable it during development. With cabal-install you can `cabal install aeson -ffast` and with stack you can add a flag section to your stack.yaml:
260* Added list specific members to `ToJSON` and `FromJSON` classes. In
261 the same way `Read` and `Show` handle lists specifically. This
262 removes need for overlapping instances to handle `String`.
264* Added a new `sumEncoding` option `UntaggedValue` which prevents
265 objects from being tagged with the constructor name.
267* JSONPaths are now tracked in instances derived with template-haskell
270* Get rid of redundancy of JSONPath error messages in nested records.
272 `eitherDecode "{\"x\":{\"a\": [1,2,true]}}" :: Either String Y`
274 `Error in $.x.a[2]: failed to parse field" x: failed to parse field a: expected Int, encountered Boolean`
275 and now yields `Error in $.x.a[2]: expected Int, encountered Boolean"`.
277 Some users might prefer to insert `modifyFailure` themselves to
278 customize error messages, which previously prevented the use of
281* Backwards compatibility with `bytestring-0.9` using the
282 `bytestring-builder` compatibility package.
284* Export `decodeWith`, `decodeStrictWith`, `eitherDecodeWith`, and
285 `eitherDecodeStrictWith` from `Data.Aeson.Parser`. This allows
286 decoding using explicit parsers instead of using `FromJSON`
289* Un-orphan internal instances to render them in haddocks.
293* Integral `FromJSON` instances now only accept integral
294 values. E.g. parsing `3.14` to `Int` fails instead of succeeding
297* Over/underflows are now caught for bounded numeric types.
299* Remove the `contents` field encoding with `allNullaryToStringTag = False`,
300 giving us `{ "tag" : "c1" }` instead of `{ "tag" : "c1", contents : [] }`.
301 The contents field is optional when parsing so this is only a breaking
302 change for ToJSON instances.
304* Fix a bug where `genericToEncoding` with `unwrapUnaryRecords = True`
305 would produce an invalid encoding: `"unwrap\":""`.
307* `ToJSON` instances using `genericToEncoding` and `omitNothingFields`
308 no longer produce invalid JSON.
310* Added instances for `DList`, `Compose`, `Product`, `Sum`.
314* Enable `PolyKinds` to generalize `Proxy`, `Tagged`, and `Const` instances.
315* Add `unsafeToEncoding` in `Data.Aeson.Types`, use with care!
319* Fix build with `base >= 4.8` and `unordered-containers < 0.2.6`.
323* Fix build on TH-less GHCs
327* Fix build with `base < 4.8` and `unordered-containers < 0.2.6`.
328* Add missing field in docs for `defaultOptions`.
332* Fixes a bug where the hashes of equal values could differ.
336The only changes are added instances.
339* `ToJSON a => ToJSON (NonEmpty a)`
340* `FromJSON a => FromJSON (NonEmpty a)`
342* `FromJSON (Proxy a)`
343* `ToJSON b => ToJSON (Tagged a b)`
344* `FromJSON b => FromJSON (Tagged a b)`
345* `ToJSON a => ToJSON (Const a b)`
346* `FromJSON a => FromJSON (Const a b)`
348These are now available for older GHCs:
354This release should be close to backwards compatible with aeson 0.9.
356If you are upgrading from aeson 0.10 it might be easier to go back in
357history to the point you were still using 0.9.
361* Revert `.:?` to behave like it did in 0.9. If you want the 0.10
362 behavior use `.:!` instead.
364* Revert JSON format of `Either` to 0.9, `Left` and `Right` are now
365 serialized with an initial uppercase letter. If you want the names
366 in lowercase you can add a newtype with an instance.
368* All `ToJSON` and `FromJSON` instances except for `[a]` are no longer
369 `OVERLAPPABLE`. Mark your instance as `OVERLAPPING` if it overlaps
370 any of the other aeson instances.
372* All `ToJSON` and `FromJSON` instances except for `[Char]` are no
373 longer incoherent, this means you may need to replace your
374 incoherent instances with a newtyped instance.
378* Introduce `.:!` that behaves like `.:?` did in 0.10.
380* Allow `HH:MM` format for `ZonedTime` and `UTCTime`.
381 This is one of the formats allowed by
382 [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601#Times).
384* Added `ToJSON` and `FromJSON` instances for the
385 `Version`, `Ordering`, and `Natural` types.
389* JSONPath identifiers are now escaped if they contain invalid characters.
391* Fixed JSONPath messages for Seq to include indices.
393* Fixed JSONPath messages for Either to include `left`/`right`.
395* Fix missing quotes surrounding time encodings.
397* Fix #293: Type error in TH when using `omitNothingFields = True`.
401* Various updates to support GHC 8.
406## Performance improvements
408* Direct encoding via the new `toEncoding` method is over 2x faster
409 than `toJSON`. (You must write or code-gen a `toEncoding`
410 implementation to unlock this speedup. See below for details.)
412* Improved string decoding gives a 12% speed win in parsing
413 string-heavy JSON payloads (very common).
415* Encoding and decoding of time-related types are 10x faster (!!) as a
416 result of bypassing `Data.Time.Format` and the arbitrary-precision
419* When using `toEncoding`, `[Char]` can be encoded without a conversion to
420 `Text`. This is fast and efficient.
422* Parsing into an `Object` is now 5% faster and more
423 allocation-efficient.
425## SUBTLE API CHANGES, READ CAREFULLY
427With the exception of long-deprecated code, the API changes below
428**should be upwards compatible** from older versions of `aeson`. If you run
429into upgrade problems, please file an issue with details.
431* The `ToJSON` class has a new method, `toEncoding`, that allows
432 direct encoding from a Haskell value to a lazy bytestring without
433 construction of an intermediate `Value`.
435 The performance benefits of direct encoding are significant: more
436 than 2x faster than before, with less than 1/3 the memory usage.
438 To preserve API compatibility across upgrades from older versions of
439 this library, the default implementation of `toEncoding` uses
440 `toJSON`. You will *not* see any performance improvement unless you
441 write an implementation of `toEncoding`, which can be very simple:
444 instance ToJSON Coord where
445 toEncoding = genericToEncoding defaultOptions
448 (Behind the scenes, the `encode` function uses `toEncoding` now, so
449 if you implement `toEncoding` for your types, you should see a
450 speedup immediately.)
452 If you use Template Haskell or GHC Generics to auto-generate your
453 `ToJSON` instances, you'll benefit from fast toEncoding
454 implementations for free!
456* When converting from a `Value` to a target Haskell type, `FromJSON`
457 instances now provide much better error messages, including a
458 complete JSON path from the root of the object to the offending
459 element. This greatly eases debugging.
461* It is now possible to use Template Haskell to generate `FromJSON`
462 and `ToJSON` instances for types in data families.
464* If you use Template Haskell or generics, and used to use the
465 `camelTo` function to rename fields, the new `camelTo2` function is
466 smarter. For example, `camelTo` will rename `CamelAPICase` to
467 `camelapi_case` (ugh!), while `camelTo2` will map it to
468 `camel_api_case` (yay!).
470* New `ToJSON` and `FromJSON` instances for the following time-related
471 types: `Day`, `LocalTime`.
473* `FromJSON` `UTCTime` parser accepts the same values as for `ZonedTime`,
474 but converts any time zone offset into a UTC time.
476* The `Result` type is now an instance of `Foldable` and `Traversable`.
478* The `Data.Aeson.Generic` module has been removed. It was deprecated in
481* GHC 7.2 and older are no longer supported.
483* The instance of `Monad` for the `Result` type lacked an implementation
484 of `fail` (oops). This has been corrected.
486* Semantics of `(.:?)` operator are changed. It's doesn't anymore accept
487 present `Null` value.
489* Added `(Foldable t, ToJSON a) => ToJSON (t a)` overlappable instance.
490 You might see `No instance for (Foldable YourPolymorphicType) arising from a
491 use of ‘.=’` -errors due this change.
495* A stray export of `encodeToBuilder` got away!
499* The `json` and `json'` parsers are now synonyms for `value` and
500 `value'`, in conformance with the looser semantics of RFC 7159.
502* Renamed `encodeToByteStringBuilder` to the more compact
507* The dependency on the `unordered-containers` package was too lax,
508 and has been corrected.
512* Encoding a `Scientific` value with a huge exponent is now handled
513 efficiently. (This would previously allocate a huge
514 arbitrary-precision integer, potentially leading to a denial of
517* Handling of strings that contain backslash escape sequences is
518 greatly improved. For a pathological string containing almost a
519 megabyte of consecutive backslashes, the new implementation is 27x
520 faster and uses 42x less memory.
522* The `ToJSON` instance for `UTCTime` is rendered with higher
523 (picosecond) resolution.
525* The `value` parser now correctly handles leading whitespace.
527* New instances of `ToJSON` and `FromJSON` for `Data.Sequence` and
528 `Data.Functor.Identity`. The `Value` type now has a `Read` instance.
530* `ZonedTime` parser ordering now favours the standard `JSON` format,
531 increasing efficiency in the common case.
533* Encoding to a `Text.Builder` now escapes `'<'` and `'>'` characters,
538* Fix `ToJSON` instance for 15-tuples (see #223).
546* Add `ToJSON` and `FromJSON` instances for tuples of up to 15
551* Major compiler and library compatibility changes: we have dropped
552 support for GHC older than 7.4, `text` older than 1.1, and
553 `bytestring` older than 0.10.4.0. Supporting the older versions had
554 become increasingly difficult, to the point where it was no longer
559* The performance of encoding to and decoding of bytestrings have both
560 improved by up to 2x, while also using less memory.
562* New dependency: the `scientific` package lets us parse floating point
563 numbers more quickly and accurately.
565* `eitherDecode`, `decodeStrictWith`: fixed bugs.
567* Added `FromJSON` and `ToJSON` instances for `Tree` and `Scientific`.
569* Fixed the `ToJSON` instances for `UTCTime` and `ZonedTime`.
573* Much improved documentation.
575* Angle brackets are now escaped in JSON strings, to help avoid XSS
578* Fixed up handling of nullary constructors when using generic
581* Added `ToJSON`/`FromJSON` instances for:
584 * ISO-8601 dates: `UTCTime`, `ZonedTime`, and `TimeZone`
586* Added accessor functions for inspecting `Value`s.
588* Added `eitherDecode` function that returns an error message if
593* This release introduces a slightly obscure, but
594 backwards-incompatible, change.
596 In the generic APIs of versions 0.4 and 0.5, fields whose names
597 began with a `"_"` character would have this character removed. This
598 no longer occurs, as it was both buggy and surprising
599 (https://github.com/bos/aeson/issues/53).
601* Fixed a bug in generic decoding of nullary constructors
602 (https://github.com/bos/aeson/issues/62).
606* When used with the UTF-8 encoding performance improvements
607 introduced in version 0.11.1.12 of the `text` package, this release
608 improves `aeson`'s JSON encoding performance by 33% relative to
611 As part of achieving this improvement, an API change was necessary.
612 The `fromValue` function in the `Data.Aeson.Encode` module now uses
613 the `text` package's `Builder` type instead of the `blaze-builder`
614 package's `Builder` type.
618* The new `decode` function complements the longstanding `encode`
619 function, and makes the API simpler.
621* New examples make it easier to learn to use the package
622 (https://github.com/bos/aeson/tree/master/examples).
626 `aeson`'s support for data-type generic programming makes it
627 possible to use JSON encodings of most data types without writing
628 any boilerplate instances.
630 Thanks to Bas Van Dijk, `aeson` now supports the two major schemes
631 for doing datatype-generic programming:
633 * the modern mechanism, built into GHC itself
634 (http://www.haskell.org/ghc/docs/latest/html/users_guide/generic-programming.html)
636 * the older mechanism, based on SYB (aka "scrap your
639 The modern GHC-based generic mechanism is fast and terse: in fact,
640 its performance is generally comparable in performance to
641 hand-written and TH-derived `ToJSON` and `FromJSON` instances. To
642 see how to use GHC generics, refer to `examples/Generic.hs`.
644 The SYB-based generics support lives in `Data.Aeson.Generic` and is
645 provided mainly for users of GHC older than 7.2. SYB is far slower
646 (by about 10x) than the more modern generic mechanism. To see how
647 to use SYB generics, refer to `examples/GenericSYB.hs`.
649* We switched the intermediate representation of JSON objects from
650 `Data.Map` to `Data.HashMap` which has improved type conversion
653* Instances of `ToJSON` and `FromJSON` for tuples are between 45% and 70%
658 This version of aeson makes explicit the decoupling between
659 *identifying* an element of a JSON document and *converting* it to
660 Haskell. See the `Data.Aeson.Parser` documentation for details.
662 The normal `aeson` `decode` function performs identification
663 strictly, but defers conversion until needed. This can result in
664 improved performance (e.g. if the results of some conversions are
665 never needed), but at a cost in increased memory consumption.
667 The new `decode'` function performs identification and conversion
668 immediately. This incurs an up-front cost in CPU cycles, but
669 reduces reduce memory consumption.
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list