Tim Fischbach

Thanks for your contribution. So far I did not get around to taking a closer look. I'll be on vacation next week. So in case the PR should be ready...

Sorry for not getting back earlier. This might be a good compromise. I find the new design a bit dense and harder to read. Have you considered keeping the items...

Yeah, I thought about that as well. One could also consider integrating with or replicating Redmine's functionality to [update issues via keywords in commit messages](https://github.com/redmine/redmine/blob/c04ab14ed4843baa0a7d55fe61a7377bb4909880/app/models/changeset.rb#L225) (e.g. `closes #123`). But even...

Not at the moment. I see different options, though: * One could adjust the [controller that receives webhooks](https://github.com/tf/redmine_merge_request_links/blob/master/app/controllers/merge_requests_controller.rb#L6) to read a list of allowed projects from a query parameter in...

@k15a Prefixing the path with `./` does not change anything.

I'd be open to a PR that rewrites the import statement when we [prepare the stylesheet for the published npm package](https://github.com/codevise/activeadmin-searchable_select/blob/3e4130a5decb16b2114550e83308c5eae3d1a915/package.json#L35). The file in `app/assets/stylesheets` would still need the unaltered...

Sure, we can backport commits to stable branches and release patch level versions. Which version would you be interested in? We are currently wrapping up work on the first iteration...

Sorry for not getting back earlier. We will soon release a new version. As an alternative, I have added a wiki page that describes the steps required to [run Pageflow...

I have backported the Twitter -> X changes to 17.0.4.