summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authormorpheus65535 <[email protected]>2024-02-23 15:36:33 -0500
committerGitHub <[email protected]>2024-02-23 15:36:33 -0500
commit0293ea7896b06caede17e17561dcc197a795b81b (patch)
treec731b06fed49e5388b2c6964dc8a828b7ef6793f
parent18cbf6fd00c6d04db4b58236df6da7dca699ec62 (diff)
downloadbazarr-1.4.3-beta.2.tar.gz
bazarr-1.4.3-beta.2.zip
no log: Update CONTRIBUTING.mdv1.4.3-beta.2
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 85fb6a42c..616d74272 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -42,4 +42,4 @@ As we're using Git in the development process, you better disable automatic upda
- All commits must have a meaningful commit message (ex.: Fixed issue with this, Improved process abc, Added input field to UI, etc.).
- Fixes can be made directly to `development` branch but keep in mind that a pre-release with a beta versioning will be created every day a new push is made.
- Features must be developed in dedicated feature branch and merged back to `development` branch using PR.
-- Once reviewed, your PR will be merged using Squash and Merge with a meaningful message.
+- Once reviewed, your PR will be merged by morpheus65535 using Squash and Merge with a meaningful message.