Migration could return unreadable error messages

[kaskranenburgQ]

While running a migration I got the following error message:

Caused by:
NoMethodError: undefined method value' for nil:NilClass (NoMethodError)

        if value && value != current.find(key).value

Following this error message it was unclear where I had to fix this error message.
I could not deduce whether one of the given values, commit messages, or a combination of the two was not valid according to the migration.
While digging deeper I found that the importable_commit.rb file generated this error message, since I entered some keys in the migration that can not be altered.

I propose that we change the error message to one that is more descriptive, meaning that the error message tells you what keys you entered in the migration should be removed.

Notifying @noracato

[MartLubben]

What is the status of this issue? Will it be solved before the start of the next month?

[noracato]

@MartLubben It does not need to be solved to merge the PR with the data. We will pick this up at a later point!

[github-actions]

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.