Tim Fischbach

Sorry. I accidentally pasted the wrong stack trace :see_no_evil: Here's the correct one ``` $ bin/rake db:create:all --trace ** Invoke db:create:all (first_time) ** Invoke db:load_config (first_time) ** Invoke environment (first_time)...

Here's a [simple sample app](https://github.com/tf/db-create-all-repro) (basically just `rails new` and changes to `database.yml`) with a [GitHub Actions workflow](https://github.com/tf/db-create-all-repro/blob/main/.github/workflows/db_create_all.yml) that [reproduces the bug in 7.1.3](https://github.com/tf/db-create-all-repro/actions/runs/7561352109) and also shows that the workaround...

Alternatively, one could always create associations with at least three records in tests. This bloats test setup, though, and is easy to forget. Only using application backtraces means erring on...

Also happy to add a README section if this is not considered too much of an edge case.

Maybe the webhook sent on close [does not contain the description/body](https://github.com/tf/redmine_merge_request_links/blob/2d0e9c85387fd62dbd72f817c53c0da50ee6f40d/lib/redmine_merge_request_links/event_handlers/gitea.rb#L42)? Every time that is changed, the [linked merge requests are updated](https://github.com/tf/redmine_merge_request_links/blob/2d0e9c85387fd62dbd72f817c53c0da50ee6f40d/app/models/merge_request.rb#L24). I'm not using the Gitea integration myself. So...

Maybe we can make the [Gitea adater only update the description](https://github.com/tf/redmine_merge_request_links/blob/2d0e9c85387fd62dbd72f817c53c0da50ee6f40d/lib/redmine_merge_request_links/event_handlers/gitea.rb#L42) if the corresponding field is present? Happy to accept a PR that adds a test case similar to [the...

No. Currently there is no integration with the Redmine API.

I argee that making the tab content flow around the MR box like that is far from ideal. Turning the MRs into a tab - while being more consistent -...

Thanks for your contribution. I'll be on vacation next week, but will have a look afterwards. I took a quick peak at the code and saw that the new features...

> we might use the REDMINE_MERGE_REQUEST_LINKS_GITLAB_REDMINE_USER_ID to create journals when merge request is created or updated. Oh that could be really cool! Let's do it in a separate PR, though,...