{"push_id":713246663,"size":1,"distinct_size":0,"ref":"refs/heads/g3_v1_4","head":"f81ff3beb0c9d19d494c5878086fb57476442b8b","before":"720012eab6fef5e075a1d6876dd2e508c8e95b73","commits":[{"sha":"f81ff3beb0c9d19d494c5878086fb57476442b8b","author":{"email":"e3b6cda228242c30b711ac17cb264f1dbadfd0b6@bacondarwin.com","name":"Peter Bacon Darwin"},"message":"fix($browser): prevent infinite digest if changing hash when there is no hashPrefix\n\nThe `window.location.hash' setter will strip of a single leading hash character\nif it exists from the fragment  before joining the fragment value to the href\nwith a new hash character.\n\nThis meant that if we want the fragment to lead with a hash character, we\nmust do `window.location.hash = '##test'` to ensure that the first hash\ncharacter in the fragment is not lost.\n\nThe `$location.hash` setter works differently and assumes that the value\npassed is the the full fragment, i.e. it does not attempt to strip off a\nsingle leading hash character.\n\nPreviously, if you called, `$location.hash('#test')`, the leading hash was\nbeing stripped and the resulting url fragment did not contain this hash:\n`$location.hash()`, then became 'test' rather than `#test`, which led to\nan infinite digest.\n\nCloses #10423\nCloses #12145","distinct":false,"url":"https://api.github.com/repos/angular/angular.js/commits/f81ff3beb0c9d19d494c5878086fb57476442b8b"}]}