summaryrefslogtreecommitdiff
path: root/django/views/templates/technical_404.html
diff options
context:
space:
mode:
authorAdam Johnson <me@adamj.eu>2025-09-23 17:31:23 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2025-09-25 08:44:17 +0200
commit5cbd96003ce13621ac247f8b09c1b625daf9c7c8 (patch)
tree36a40262f17cd35710e55c8887b641a985b33cde /django/views/templates/technical_404.html
parent00174507f8a91e9577ae233c58af561b379f2695 (diff)
Removed Git attribute merge=union for release notes.
I added this back in 3222fc79431c0866aa65b2a83fbbffd2c3034d08 to try and avoid merge conflicts from concurrent edits to release notes in different branches. However, in my recent experience, it has caused more problems than it solves. I have found that when rebasing a branch that modifies a release note, it can merge sections without an intermediate blank line, leading to broken reST syntax. Example spotted in code review: https://github.com/django/django/pull/17554#discussion_r2311296513 . I think it’s better we remove this configuration and deal with merge conflicts deliberately.
Diffstat (limited to 'django/views/templates/technical_404.html')
0 files changed, 0 insertions, 0 deletions