Jakub Kašpar

Please read about the future in new topic - https://github.com/sequelpro/sequelpro/issues/3705

This project is abandoned. Try [Sequel Ace](https://github.com/Sequel-Ace/Sequel-Ace), which is an actively mantained fork.

https://github.com/sequelpro/sequelpro/issues/3705

Yes, read #3705 and switch to the SequelAce if interested.

Sequel Pro didn't get any update for years, so "after last update" probably means after OS update. Check [fork](https://github.com/Sequel-Ace/Sequel-Ace) for more updates.

https://github.com/sequelpro/sequelpro/issues/3705

Yes, happening for us too on public Open Source repo for Github Actions. Can we somehow work around that? ``` bundler: failed to load command: danger (/usr/local/lib/ruby/gems/2.6.0/bin/danger) 105 RuntimeError: Commit...

@orta Let me know if you have any idea what to do here - but it could be easy for someone who knows where is Danger looking for wrong remote?

@orta I already did today, and I think I'm not sure if `setup_danger_branches` in `github.rb:112` is getting the right stuff, if so, then `ensure_commitish_exists_on_branch` (`git_repo:99`) uses `origin` as remote and...

And isn't that exactly the problem? ``` github.rb:112:in `setup_danger_branches' ``` which means ``` scm.ensure_commitish_exists_on_branch! head_branch, head_commit ``` raises an issue... It seems like `git_fetch_branch_to_depth`is fetching from wrong place then: https://github.com/danger/danger/blob/c51e39c61c814f545c4c88c0179920684b620e56/lib/danger/scm_source/git_repo.rb#L108...