{"push_id":1032944820,"size":1,"distinct_size":1,"ref":"refs/heads/guid-escaping","head":"a845d813db8a1b5fa28e72a10ac7bbb28b7f3fc1","before":"70732350eeaa52cea1f4539816e8576e734655fe","commits":[{"sha":"a845d813db8a1b5fa28e72a10ac7bbb28b7f3fc1","author":{"email":"401f3211b78741a5069e05bda10651d6007336ed@gmail.com","name":"Duncan Brown"},"message":"Unescape GUIDs when reading from the database\n\nThis is a workaround for https://core.trac.wordpress.org/ticket/24248,\nwhich causes the 1Pass embed a problem when it reads the GUID.\nWP (and the plugin) work with an html-escaped string. By the time\nJS sees it, it has been rendered in the DOM as an unescaped string.\n\nWhen a guid contained an ampersand, this caused a hash mismatch.","distinct":true,"url":"https://api.github.com/repos/1Pass/1pass-for-wordpress/commits/a845d813db8a1b5fa28e72a10ac7bbb28b7f3fc1"}]}