)]}'
{"playbooks/proposal/kolla_check_sources.py":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"d0e3961033ec075b5a378229ecd8797b8b580173","unresolved":true,"context_lines":[{"line_number":246,"context_line":"    # than reusing the one already proposed. Reuse it if it exists, so the"},{"line_number":247,"context_line":"    # note\u0027s contents stay in sync with the current set of changes."},{"line_number":248,"context_line":"    notes_dir \u003d os.path.join(repo_root, \u0027releasenotes\u0027, \u0027notes\u0027)"},{"line_number":249,"context_line":"    existing \u003d glob.glob(os.path.join(notes_dir, f\"{slug}-*.yaml\"))"},{"line_number":250,"context_line":"    if existing:"},{"line_number":251,"context_line":"        note_path \u003d existing[0]"},{"line_number":252,"context_line":"    else:"}],"source_content_type":"text/x-python","patch_set":2,"id":"c5a11070_67d456fc","line":249,"updated":"2026-10-19 08:24:43.000000000","message":"I don\u0027t think that it can work this way, like we already have 7 `update-external-components-*` notes, and this would then always just update the first one?\n\nI think you\u0027d rather only have to check what is within the current change (if there is one) that is getting updated?\n\nalso think about the case that the existing change has e.g. an update-external-grafana that needs to change to update-external-components when another component gets updated, too?","commit_id":"e6853f04a7190a55d8ac173a0e26bca605e42aa5"}]}