From 5fd2970331cd4685e3d1ab34474c2bbaf13a59f8 Mon Sep 17 00:00:00 2001 From: tadoogie Date: Thu, 16 Apr 2026 17:20:21 +0100 Subject: [PATCH 01/16] Add workflow to block forbidden paths in PRs --- .github/workflows/block-forbidden-paths.yml | 26 +++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 .github/workflows/block-forbidden-paths.yml diff --git a/.github/workflows/block-forbidden-paths.yml b/.github/workflows/block-forbidden-paths.yml new file mode 100644 index 0000000..3c0fde6 --- /dev/null +++ b/.github/workflows/block-forbidden-paths.yml @@ -0,0 +1,26 @@ +name: Block suggestion folders from main + +on: + pull_request: + branches: + - main + +jobs: + check-forbidden-paths: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + + - name: Prevent suggestion folders being merged into main + run: | + FORBIDDEN_PATHS=( + "splitleaf-data/texts/suggestions/" + "splitleaf-data/tunes/suggestions/" + ) + + for path in "${FORBIDDEN_PATHS[@]}"; do + if git diff --name-only origin/main...HEAD | grep "^${path}"; then + echo "❌ Files in ${path} are development-only and must not be merged into main." + exit 1 + fi + done From 59bb6a0ee5a13ad4650997ad00715a1d4eb6bfbb Mon Sep 17 00:00:00 2001 From: tadoogie Date: Thu, 16 Apr 2026 18:12:31 +0100 Subject: [PATCH 02/16] Revise welcome message and add editing guidelines Updated the welcome message and added a section for editing data content. --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 59d0ac5..7e2e9be 100644 --- a/README.md +++ b/README.md @@ -1,13 +1,15 @@

Splitleaf Logo
-

Welcome to the Digital Splitleaf GitHub community!

+

Welcome to the Digital Splitleaf Data Repository!

This space supports the development, preservation, and accessibility of resources that promote **psalm singing** around the world. Whether you're here to contribute, learn, collaborate, or ask questions, we’re glad you’ve joined us. Visit the main website at **[splitleaf.org](https://splitleaf.org)** to explore our broader mission and to view editions of the data found here. --- +## Editing Data Content for the Digital Splitleaf +This repository is for you to help edit content published on the Digital Splitleaf. If you would like to suggest new editions or tunes, please visit the suggestions repository: **[https://github.com/Digital-Splitleaf/splitleaf-suggestions](https://github.com/Digital-Splitleaf/splitleaf-suggestions)** ## πŸ“– About the Digital Splitleaf From e4df2cecf224ea36346de16387eaf8f3bca358aa Mon Sep 17 00:00:00 2001 From: tadoogie Date: Thu, 16 Apr 2026 18:13:22 +0100 Subject: [PATCH 03/16] Add emoji to section header in README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7e2e9be..7f91a95 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ This space supports the development, preservation, and accessibility of resource Visit the main website at **[splitleaf.org](https://splitleaf.org)** to explore our broader mission and to view editions of the data found here. --- -## Editing Data Content for the Digital Splitleaf +## ✏️ Editing Data Content for the Digital Splitleaf This repository is for you to help edit content published on the Digital Splitleaf. If you would like to suggest new editions or tunes, please visit the suggestions repository: **[https://github.com/Digital-Splitleaf/splitleaf-suggestions](https://github.com/Digital-Splitleaf/splitleaf-suggestions)** ## πŸ“– About the Digital Splitleaf From d76158e6ddf931b9f314a17efcdcfee797b7b89f Mon Sep 17 00:00:00 2001 From: tadoogie Date: Thu, 16 Apr 2026 18:13:39 +0100 Subject: [PATCH 04/16] Add 'About the Digital Splitleaf' section to README --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 7f91a95..130bd9e 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,7 @@ Visit the main website at **[splitleaf.org](https://splitleaf.org)** to explore ## ✏️ Editing Data Content for the Digital Splitleaf This repository is for you to help edit content published on the Digital Splitleaf. If you would like to suggest new editions or tunes, please visit the suggestions repository: **[https://github.com/Digital-Splitleaf/splitleaf-suggestions](https://github.com/Digital-Splitleaf/splitleaf-suggestions)** +--- ## πŸ“– About the Digital Splitleaf Splitleaf is dedicated to: From a99b3e7e80870b27e552ae55bddecd651df6c75e Mon Sep 17 00:00:00 2001 From: tadoogie Date: Thu, 16 Apr 2026 18:13:49 +0100 Subject: [PATCH 05/16] Add 'About the Digital Splitleaf' section to README --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 7f91a95..130bd9e 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,7 @@ Visit the main website at **[splitleaf.org](https://splitleaf.org)** to explore ## ✏️ Editing Data Content for the Digital Splitleaf This repository is for you to help edit content published on the Digital Splitleaf. If you would like to suggest new editions or tunes, please visit the suggestions repository: **[https://github.com/Digital-Splitleaf/splitleaf-suggestions](https://github.com/Digital-Splitleaf/splitleaf-suggestions)** +--- ## πŸ“– About the Digital Splitleaf Splitleaf is dedicated to: From 9ea882c6deff36144caa5772efd92ed531b8dae4 Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 20:50:10 +0100 Subject: [PATCH 06/16] Remove editing data content section from README Removed section about editing data content for the Digital Splitleaf. --- README.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/README.md b/README.md index 130bd9e..44ff730 100644 --- a/README.md +++ b/README.md @@ -7,10 +7,6 @@ This space supports the development, preservation, and accessibility of resource Visit the main website at **[splitleaf.org](https://splitleaf.org)** to explore our broader mission and to view editions of the data found here. ---- -## ✏️ Editing Data Content for the Digital Splitleaf -This repository is for you to help edit content published on the Digital Splitleaf. If you would like to suggest new editions or tunes, please visit the suggestions repository: **[https://github.com/Digital-Splitleaf/splitleaf-suggestions](https://github.com/Digital-Splitleaf/splitleaf-suggestions)** - --- ## πŸ“– About the Digital Splitleaf From 62aac402bd0604f0ec136e3771b514a39decd187 Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 20:52:09 +0100 Subject: [PATCH 07/16] Update CONTRIBUTING.md with pull request guidelines Added guidelines for using GitHub pull requests and anonymity. --- CONTRIBUTING.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 657a3dd..9c4b997 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -62,6 +62,23 @@ In the processing folder, files can be edited by any user. Before any file can b No submission will advance to publication without these dual approvals. +This project uses GitHub pull requests as its formal editorial +and validation mechanism. + +- Editors and validators are recorded automatically after a pull + request is merged. +- Contributors should not manually edit editorial metadata + (e.g. , ). + +**Anonymity** +If you wish to be credited anonymously: +- Editors: include the word "anonymous" in the pull request description. +- Validators: include the word "anonymous" in your approval comment. + +GitHub identities are retained internally for audit purposes, but +may not appear in published files. + + *** ### 5. Review of Submitted Changes From 885c5170cece6c72b4cf4b563365fd15e55a9961 Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 20:52:31 +0100 Subject: [PATCH 08/16] Include instructions for anonymous contributions Added guidelines for anonymous contributions. --- CONTRIBUTING.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9c4b997..38475b3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -71,6 +71,7 @@ and validation mechanism. (e.g. , ). **Anonymity** + If you wish to be credited anonymously: - Editors: include the word "anonymous" in the pull request description. - Validators: include the word "anonymous" in your approval comment. From 6ed128a89621d99322ebfaf4b400f06dd5a9618b Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 20:53:32 +0100 Subject: [PATCH 09/16] Clarify editorial metadata editing instructions Removed instructions regarding manual editing of editorial metadata. --- CONTRIBUTING.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 38475b3..0886048 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -66,9 +66,7 @@ This project uses GitHub pull requests as its formal editorial and validation mechanism. - Editors and validators are recorded automatically after a pull - request is merged. -- Contributors should not manually edit editorial metadata - (e.g. , ). + request is merged.. **Anonymity** From f91016d058c75524a2cdc9014d067d7c5e3ff9ac Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 20:57:56 +0100 Subject: [PATCH 10/16] Reorganize steps for editing and approval process --- texts/README.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/texts/README.md b/texts/README.md index ac9e619..0d829e5 100644 --- a/texts/README.md +++ b/texts/README.md @@ -12,17 +12,19 @@ To ensure the highest accuracy, every file must be edited or verified by **two d 1. **Switch to Development:** Click the branch selector (labeled `main`) at the top left and select **`development`**. 2. **Find your File:** Navigate to the XML file you wish to edit. 3. **Edit:** Click the **Pencil Icon**. Edit the file according to the **Community Editing Priorities** below. -4. **Add:** Add your name and initials to the header file under Validator 1. -5. **Save:** Scroll to the bottom, write a short note of your changes, and click **Commit changes**. -6. **Propose:** Click the green **"Compare & pull request"** button. Ensure the "base" is `main` and "compare" is `development`. Click **Create pull request**. +4. **Save:** Scroll to the bottom, write a short note of your changes, and click **Commit changes**. +5. **Propose:** Click the green **"Compare & pull request"** button. Ensure the "base" is `main` and "compare" is `development`. Click **Create pull request**. ### Step 2: The Peer Review (Editor 2) 1. **Review:** Open a pending Pull Request and click the **Files changed** tab. 2. **Verify:** Check the XML against the original source and the **Community Priorities** below. -3. **Add:** Add your name and initials to the header file under Validator 2. -4. **Approve:** Click **Review changes**, select **Approve**, and submit. +3. **Approve:** Click **Review changes**, select **Approve**, and submit. -### Step 3: Admin Final Approval +### Step 3: Auto Attribution +- Editors and validators will be recorded automatically after a pull request is merged (approved). +- **Anonymity**: If you wish to be credited anonymously, include the word "anonymous" in the request description or approval comment. + +### Step 4: Admin Final Approval Admins are automatically notified via `CODEOWNERS`. We perform a final technical check and **Merge** the file to `main`, which pushes it live to the website. --- From 59477adc06addb8dba1f5c2a67b3297e1c1bd65c Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 21:02:11 +0100 Subject: [PATCH 11/16] Revise editing process and add auto attribution section Updated editing steps to include auto attribution and anonymity options. --- tunes/readme.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/tunes/readme.md b/tunes/readme.md index c031b73..cf93857 100644 --- a/tunes/readme.md +++ b/tunes/readme.md @@ -12,17 +12,19 @@ To ensure the highest accuracy, every file must be edited or verified by **two d 1. **Switch to Development:** Click the branch selector (labeled `main`) at the top left and select **`development`**. 2. **Find your File:** Navigate to the XML file you wish to edit. 3. **Edit:** Click the **Pencil Icon** at the top right of the code pane. Edit the file according to the **Community Editing Priorities** below. -4. **Add:** Add your name and initials to the header file under Validator 1. 5. **Save:** Scroll to the bottom, write a short note of your changes, and click **Commit changes**. 6. **Propose:** Click the green **"Compare & pull request"** button. Ensure the "base" is `main` and "compare" is `development`. Click **Create pull request**. ### Step 2: The Peer Review (Editor 2) 1. **Review:** Open a pending Pull Request and click the **Files changed** tab. 2. **Verify:** Check the XML against the original source and the **Community Priorities** below. -3. **Add:** Add your name and initials to the header file under Validator 2. 4. **Approve:** Click **Review changes**, select **Approve**, and submit. -### Step 3: Admin Final Approval +### Step 3: Auto Attribution +- Editors and validators will be recorded automatically after a pull request is merged (approved). +- **Anonymity**: If you wish to be credited anonymously, include the word "anonymous" in the request description or approval comment. + +### Step 4: Admin Final Approval Admins are automatically notified via `CODEOWNERS`. We perform a final technical check and **Merge** the file to `main`, which pushes it live to the website. --- From 10e56429db8b90b46d3bed173869b5ec018a4f8d Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 21:04:13 +0100 Subject: [PATCH 12/16] Revise readme for music file submissions Updated the readme to include guidelines for suggesting new tune editions and preferred file formats. --- tunes/incoming/readme.md | 1 - tunes/suggestions/readme.md | 11 +++++++++++ 2 files changed, 11 insertions(+), 1 deletion(-) delete mode 100644 tunes/incoming/readme.md create mode 100644 tunes/suggestions/readme.md diff --git a/tunes/incoming/readme.md b/tunes/incoming/readme.md deleted file mode 100644 index 3978719..0000000 --- a/tunes/incoming/readme.md +++ /dev/null @@ -1 +0,0 @@ -This is the place to uploade your music files. diff --git a/tunes/suggestions/readme.md b/tunes/suggestions/readme.md new file mode 100644 index 0000000..95a5d2e --- /dev/null +++ b/tunes/suggestions/readme.md @@ -0,0 +1,11 @@ +## Suggest new tune editions here +Upload your suggested tunes into this folder. We prefer the following file formats: +- musicXML (.xml OR .musicxml) +- MuseScore (.mscz) +- Music Encoding Initiative (.xml) + +Most music notation software should be able to export files to musicXML or MEI. See your software's instructions for creating these files. + +### Important notes +1. We can accept other file formats (PDF, etc.). However, it may take us some time to process them. We may have to clean-up or re-create the music files using MuseScore. +2. We cannot publish any content without copyright permission. We may, therefore, contact you for help in getting that permission. From 81ffe3ea202c0c823bcb5d46a326d2e10b33d4bc Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 21:05:39 +0100 Subject: [PATCH 13/16] Update readme with branch switching instructions Added instructions to switch to the 'Development' branch before uploading suggested tunes. --- tunes/suggestions/readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tunes/suggestions/readme.md b/tunes/suggestions/readme.md index 95a5d2e..29d4a10 100644 --- a/tunes/suggestions/readme.md +++ b/tunes/suggestions/readme.md @@ -1,5 +1,5 @@ ## Suggest new tune editions here -Upload your suggested tunes into this folder. We prefer the following file formats: +Swith to the 'Development' branch in the top left (you may see 'main' right now). Upload your suggested tunes into this folder. We prefer the following file formats: - musicXML (.xml OR .musicxml) - MuseScore (.mscz) - Music Encoding Initiative (.xml) From 7235ec8dc916d3e4b8bf44b5bf2f049b1323fb26 Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 21:07:03 +0100 Subject: [PATCH 14/16] Rename readme.md to readme.md --- {tunes/suggestions => suggestions/tunes}/readme.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename {tunes/suggestions => suggestions/tunes}/readme.md (100%) diff --git a/tunes/suggestions/readme.md b/suggestions/tunes/readme.md similarity index 100% rename from tunes/suggestions/readme.md rename to suggestions/tunes/readme.md From ae7c4cb0801070573797b77a3d99afd14c5ed9a7 Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 21:08:46 +0100 Subject: [PATCH 15/16] Create readme.md --- suggestions/texts/readme.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 suggestions/texts/readme.md diff --git a/suggestions/texts/readme.md b/suggestions/texts/readme.md new file mode 100644 index 0000000..b7886fb --- /dev/null +++ b/suggestions/texts/readme.md @@ -0,0 +1,23 @@ +## Suggest new text editions here +Upload your suggested texts into this folder. Be sure that you are in the 'development' brancn in the top left (you may see 'main' instead). If possible, please upload a .txt file of your Psalm(s) that employs the following format for **each** psalm. If you do not know some of this information, you can leave it blank. However, please add an empty line between the header and title (metre), and another between the title (metre) and the first stanza. Each subsequent stanza should have a blank line before it. +``` +Long Title: The Psalms of David in Metre +Short Title: Psalms in Metre +Publisher: Church of Scotland +Date: 1650 + +Psalm 21 (CM) + +1 The king in thy great strength, O Lord, +Shall very joyful be; +In thy salvation rejoice +How vehemently shall he! + +2 Thou hast bestowed upon him all +That his heart would request; +And thou from him didst not withhold +Whate'er his lips expressed. +``` +### Important notes +1. We can accept other file formats (Word, PDF, etc.). However, it may take us some time to process them. We will have to format the texts as described above. +2. We cannot publish any content without copyright permission. We may, therefore, contact you for help in getting that permission. From eadcfd44932951b6559c0c7b8d37f9ec6c259b76 Mon Sep 17 00:00:00 2001 From: tadoogie Date: Fri, 17 Apr 2026 21:13:27 +0100 Subject: [PATCH 16/16] Create readme.md for content suggestions Added guidelines for content suggestions in the readme. --- suggestions/readme.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 suggestions/readme.md diff --git a/suggestions/readme.md b/suggestions/readme.md new file mode 100644 index 0000000..e05ab9e --- /dev/null +++ b/suggestions/readme.md @@ -0,0 +1,6 @@ +## Content Suggestions ## +We welcome your suggestions for content to be added to the Digital Splitleaf. Please note that we can only publish content in the public domain or with the permission of copyright holders. + +If you would like to contribute, ensure you are viewing the **development** branch. If you see **main** at the top left, click it and switch to **development**. + +Then, select the folder based on the type of content that you would like to add.