Handling pre-commit config files

[AntoineD]

When a template has a pre-commit config file that is updated independently of copier, applying copier update yields conflicts on the lines that define the hook versions.
Is there a way to prevent copier from updating those lines?

[sisp]

Let me confirm I understand your question correctly:

You have a Copier template with a file .pre-commit-config.yaml with content similar to this:

repos:
  - repo: https://github.com/asottile/pyupgrade
    rev: v3.15.1
    hooks:
      - id: pyupgrade
        args: [--py38-plus]

You generate a project and this file is then part of the generated project. Now, pyupgrade v3.15.2 gets released and you update the version in the generated project (manually or using some update bot/tool):

 repos:
   - repo: https://github.com/asottile/pyupgrade
-    rev: v3.15.1
+    rev: v3.15.2
     hooks:
       - id: pyupgrade
         args: [--py38-plus]

What about your Copier template? Do you also update the hook version there prior to running copier update? I have a suspicion that you're seeing a merge conflict where both resolution options are identical.

Would you mind sharing the snippet of the merge conflict?

[AntoineD]

I totally forgot about this and unfortunately I no longer recall how this was happening!

I'm sorry about that and thank you for taking the time to answer.

I'm closing it for now.