Possible short term workaround would be to try to rebase that branch against main. For background context this branch exists because David was working towards doing something with timeouts https://github.com/heroku/hatchet/pull/158, but that never panned out.
Longer term: We should find a way to get this repo back on main so we're not working on a long lived branch.
I'm trying to upgrade everyone's
heroku_hatchetgem to the latest due to https://github.com/heroku/hatchet/pull/210. But can't because this repo is using a branch: https://github.com/heroku/heroku-buildpack-php/blob/dd69b2ae22209a47fe4038fd32abd3bdf0eaa2a1/Gemfile#L5Possible short term workaround would be to try to rebase that branch against main. For background context this branch exists because David was working towards doing something with timeouts https://github.com/heroku/hatchet/pull/158, but that never panned out.
Longer term: We should find a way to get this repo back on main so we're not working on a long lived branch.