{"push_id":3114887794,"size":2,"distinct_size":1,"ref":"refs/heads/lowell/verify_access_on_task_update","head":"11f51267a47e995cef1bd9901a107cc0e47f0908","before":"d25abab1c7e661b51533f7d3fa36a6d3838997b2","commits":[{"sha":"435bf01c75fbec0a5328ad59e9bc30ec22ba6437","author":{"name":"Kenshiro Nakagawa","email":"0cd5f1043292f3613471226572765685b423de86@gmail.com"},"message":"Subclass transient BGSSyncErrors (#8120)\n\n### Description\r\nWe get a lot of transient errors during end product establishment EP sync, which is polluting the alerts channel. I've been collecting which errors are transient or expected due to routine BGS maintenance, and a subclass of BGSSyncError will help treat these errors differently within our error reporting tools.\r\n\r\nNote that this PR alone does not increase/decrease the number of reported errors, just creates a subclass so we can control how they report/are consumed.\r\n\r\n### Acceptance Criteria\r\n- Transient errors during BGS EP sync are reported separately in Sentry","distinct":false,"url":"https://api.github.com/repos/department-of-veterans-affairs/caseflow/commits/435bf01c75fbec0a5328ad59e9bc30ec22ba6437"},{"sha":"11f51267a47e995cef1bd9901a107cc0e47f0908","author":{"name":"Lowell Wood","email":"75091d3c7856f46f2a9f1bacdcfd08d8ad8d89ff@users.noreply.github.com"},"message":"Merge branch 'master' into lowell/verify_access_on_task_update","distinct":true,"url":"https://api.github.com/repos/department-of-veterans-affairs/caseflow/commits/11f51267a47e995cef1bd9901a107cc0e47f0908"}]}
{"actor":{"display_login":"lowellrex"}}