From d0ae8373fe8b5a8f7ba7f62bb399d20ecdf71c08 Mon Sep 17 00:00:00 2001
From: "seedcase-sync-files-token[bot]"
<211517680+seedcase-sync-files-token[bot]@users.noreply.github.com>
Date: Fri, 23 May 2025 14:11:18 +0000
Subject: [PATCH 1/2] chore(sync): :hammer: synced file(s) with
seedcase-project/seedcase-theme
---
justfile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/justfile b/justfile
index 876b4f8..5348d89 100644
--- a/justfile
+++ b/justfile
@@ -24,7 +24,7 @@ check-commits:
number_of_commits=$(git rev-list --count HEAD ^main)
if [[ ${branch_name} != "main" && ${number_of_commits} -gt 0 ]]
then
- uvx cz check --rev-range main..HEAD
+ uvx --from commitizen cz check --rev-range main..HEAD
else
echo "Can't either be on ${branch_name} or have more than ${number_of_commits}."
fi
From 6417850a96004a70690cb4df8700b789a69938ef Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
<66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Fri, 23 May 2025 14:11:25 +0000
Subject: [PATCH 2/2] chore(pre-commit): :pencil2: automatic fixes
---
LICENSE.md | 2 +-
home.svg | 2 +-
why-cyclical-workflows/_index.qmd | 4 ++--
why-github-flow/index.qmd | 32 +++++++++++++++---------------
why-jsonschema/index.qmd | 2 +-
why-lint-with-commitizen/index.qmd | 2 +-
why-markdown/index.qmd | 2 +-
why-pytest/index.qmd | 4 ++--
8 files changed, 25 insertions(+), 25 deletions(-)
diff --git a/LICENSE.md b/LICENSE.md
index 0fb847e..521adbb 100644
--- a/LICENSE.md
+++ b/LICENSE.md
@@ -49,7 +49,7 @@ exhaustive, and do not form part of our licenses.
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More considerations
- for the public:
+ for the public:
wiki.creativecommons.org/Considerations_for_licensees
=======================================================================
diff --git a/home.svg b/home.svg
index 088d7d7..8700475 100644
--- a/home.svg
+++ b/home.svg
@@ -1 +1 @@
-
\ No newline at end of file
+
diff --git a/why-cyclical-workflows/_index.qmd b/why-cyclical-workflows/_index.qmd
index c5f6e05..a59c717 100644
--- a/why-cyclical-workflows/_index.qmd
+++ b/why-cyclical-workflows/_index.qmd
@@ -4,9 +4,9 @@ description: ""
date: ""
draft: true
# categories:
-# -
+# -
---
Follow the tidyverse team approach to repo development, by dedicating periods of time to specific repos, and rotating between.
-
\ No newline at end of file
+
diff --git a/why-github-flow/index.qmd b/why-github-flow/index.qmd
index dc78319..690bec1 100644
--- a/why-github-flow/index.qmd
+++ b/why-github-flow/index.qmd
@@ -8,63 +8,63 @@ categories:
references:
- id: sooni
title: A guide to trunk-based development (LogRocket)
- author:
+ author:
family: Sooni
given: S
- issued:
+ issued:
year: 2023
URL: https://blog.logrocket.com/product-management/a-guide-to-trunk-based-development/#whatistrunkbaseddevelopment
- id: tilburg
title: Git Branching Strategies (Tilburg Science Hub)
- author:
+ author:
family: Ambroziak
given: Paulina
- issued:
+ issued:
year: n.d.
URL: https://tilburgsciencehub.com/building-blocks/collaborate-and-share-your-work/use-github/git-branching-strategies/
- id: tbd
title: Trunk-based development
- author:
+ author:
family: Hammant,
given: Paul
- issued:
+ issued:
year: 2017-2020
URL: https://trunkbaseddevelopment.com
- id: thummala
title: "Choosing the Right Git Branching Strategy: A Comparative Analysis"
- author:
+ author:
family: Thummala
given: S
- issued:
+ issued:
year: 2023
URL: https://medium.com/@sreekanth.thummala/choosing-the-right-git-branching-strategy-a-comparative-analysis-f5e635443423#
- id: driessen
title: A successful Git branching model
- author:
+ author:
family: Driessen
given: V
- issued:
+ issued:
year: 2010
URL: https://nvie.com/posts/a-successful-git-branching-model/
- id: gitkraken
title: What is the best Git branch strategy?
- author:
+ author:
family: GitKraken
- issued:
+ issued:
year: n.d.
URL: https://www.gitkraken.com/learn/git/best-practices/git-branch-strategy
- id: githubflowpost
title: GitHub Flow - The best way to use Git and GitHub
- author:
+ author:
family: GitHub
- issued:
+ issued:
year: n.d.
URL: https://githubflow.github.io
- id: githubflow
title: GitHub flow - Follow GitHub flow to collaborate on projects.
- author:
+ author:
family: GitHub
- issued:
+ issued:
year: n.d.
URL: https://docs.github.com/en/get-started/quickstart/github-flow
diff --git a/why-jsonschema/index.qmd b/why-jsonschema/index.qmd
index 314ef68..501e72b 100644
--- a/why-jsonschema/index.qmd
+++ b/why-jsonschema/index.qmd
@@ -1,7 +1,7 @@
---
title: "Why `jsonschema`"
description: |
- As we follow the Data Package standard for structuring metadata, we have to make sure that our metadata files conform to this standard.
+ As we follow the Data Package standard for structuring metadata, we have to make sure that our metadata files conform to this standard.
This post explains why we chose `jsonschema` for automating the process of checking metadata files and objects against the standard.
date: "2024-11-07"
categories:
diff --git a/why-lint-with-commitizen/index.qmd b/why-lint-with-commitizen/index.qmd
index ea69971..e270f9d 100644
--- a/why-lint-with-commitizen/index.qmd
+++ b/why-lint-with-commitizen/index.qmd
@@ -133,7 +133,7 @@ conventional commits standard and checks to ensure that standard is followed.
### gitlint
-Gitlint checks your commit messages for style.
+Gitlint checks your commit messages for style.
::::: columns
::: column
diff --git a/why-markdown/index.qmd b/why-markdown/index.qmd
index aac2c5b..888c4b3 100644
--- a/why-markdown/index.qmd
+++ b/why-markdown/index.qmd
@@ -81,7 +81,7 @@ editor.
- Because of it's ease of use, there are some more powerful features
that are not implemented in the original Markdown syntax, so
extensions are needed to use features that may be needed in some
- cases. For instance, they can't handle special formatting around text
+ cases. For instance, they can't handle special formatting around text
like a "callout" block often used on websites or in books to draw attention
to a tip or important piece of information.
:::
diff --git a/why-pytest/index.qmd b/why-pytest/index.qmd
index 82b4a37..996a9f2 100644
--- a/why-pytest/index.qmd
+++ b/why-pytest/index.qmd
@@ -1,8 +1,8 @@
---
title: "Why Pytest"
description: |
- Testing software is a requirement for ensuring it works as intended and because we use a test-driven development workflow.
- This post explains why we choose to use pytest over the built-in
+ Testing software is a requirement for ensuring it works as intended and because we use a test-driven development workflow.
+ This post explains why we choose to use pytest over the built-in
unittest framework for testing Python code.
date: "2024-07-17"
categories: