From 985a2f0f74cc3f574054fe47a42341965f402611 Mon Sep 17 00:00:00 2001
From: Paul Latzelsperger <paul.latzelsperger@beardyinc.com>
Date: Tue, 11 Apr 2023 09:02:51 +0200
Subject: [PATCH] fix: add newline to file
---
.github/workflows/verify.yaml | 2 --
.../decision-records/2023-04-03_renaming_branches/README.md | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/.github/workflows/verify.yaml b/.github/workflows/verify.yaml
index b51c482f1..c9c8f1d5f 100644
--- a/.github/workflows/verify.yaml
+++ b/.github/workflows/verify.yaml
@@ -34,8 +34,6 @@ on:
pull_request:
paths-ignore:
- 'charts/**'
- - 'docs/**'
- - '**/*.md'
branches:
- '*'
workflow_dispatch:
diff --git a/docs/development/decision-records/2023-04-03_renaming_branches/README.md b/docs/development/decision-records/2023-04-03_renaming_branches/README.md
index 7bc3abd64..5638a79dd 100644
--- a/docs/development/decision-records/2023-04-03_renaming_branches/README.md
+++ b/docs/development/decision-records/2023-04-03_renaming_branches/README.md
@@ -58,4 +58,4 @@ like force-pushing. Write access to `upstream` is required!_
The new `releases` branch (note the plural) will serve the same purpose that `main` did up until now, which is to track
all releases (via merge commits and tags) in chronological order. We will continue to have separate `release/x.y.z`
-branches for every release.
\ No newline at end of file
+branches for every release.