Automatically resolve conflicts in yarn.lock about backport HOT 3 CLOSED

backport being a useful tool outside the realm of javascript I'm hesitant to implement something language specific like this.

For a while I've been thinking about changing the project config (.backportrc.json) from json to js. This would allow users to implement pre- and post-backport hooks.

Something like this could then be implemented:

module.exports = {
  upstream: 'elastic/kibana',
  onConflict: async (files) => {
    if(files.includes('yarn.lock')) {
      return exec('yarn kbn bootstrap');
    }
  }
}

What do you think?

from backport.

I'm not opposed, but would only want to handle automatic conflict resolution when the files were exactly just yarn.lock, but that happens less and less these days (in my experience) so I don't see it as particularly valuable.

from backport.

but that happens less and less these days (in my experience) so I don't see it as particularly valuable.

In that case, do you think this issue should be closed?

from backport.