chore(sync): 🔨 synced file(s) with seedcase-project/seedcase-theme

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
 
 =======================================================================

guides/adding-posts.qmd

@@ -81,26 +81,26 @@ Regardless, in both routes the steps are:
         the commands to run for that:
 
         ``` bash
-        # Create and move to a new branch. 
-        # Call the branch any name you want, 
+        # Create and move to a new branch.
+        # Call the branch any name you want,
         # I'll use the `adding-new-post`.
         git checkout -b adding-new-post
         # Replace `NEW_FILE` with the actual name of the file
-        git add NEW_FILE 
+        git add NEW_FILE
         # Add a short message about what you are committing
         git commit -m "New post about BRIEF_DESCRIPTION"
         # Push the changes up to GitHub
         git push origin adding-new-post
         # Switch to the main branch
         git checkout main
         ```
-        
+
         After pushing up the GitHub, you will need to go to the
         repository and create a new Pull Request from your newly pushed
         branch.
-    
+
     -   No matter if you want to add a file directly on GitHub or via the command line, you can find more guidance in the [GitHub Docs](https://docs.github.com/en/repositories/working-with-files/managing-files/adding-a-file-to-a-repository).
-        
+
 
 6.  You are all done! That's it :smile:
 

guides/index.qmd

@@ -5,7 +5,7 @@ listing:
     contents: .
     type: default
     sort: "title"
-    fields: 
+    fields:
       - "title"
       - "author"
       - "description"

index.qmd

@@ -12,4 +12,3 @@ about:
 ---
 
 ## Image from [Freepik](https://www.freepik.com) {.appendix}
-

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

learn/index.qmd

@@ -5,7 +5,7 @@ listing:
     contents: shorts
     type: default
     sort: "title"
-    fields: 
+    fields:
       - "title"
       - "author"
       - "description"

learn/shorts/_template.qmd

@@ -5,7 +5,7 @@ description: |
 author: ""
 date: ""
 # date-modified: ""
-categories: 
+categories:
   - text
 ---
 

learn/shorts/intro-gh-actions.qmd

@@ -1,14 +1,14 @@
 ---
 title: "An brief introduction to automation using GitHub Actions"
 description: |
-  The GitHub Actions feature is a powerful way of running code or a series of tasks on an 
+  The GitHub Actions feature is a powerful way of running code or a series of tasks on an
   independent and fresh computing environment. You can use these to
   automate tasks, run tasks on a schedule, test your code, or perform any number
   of tasks that you'd rather have a computer handle instead of doing manually.
 author: "Luke W. Johnston"
 date: "2024-05-21"
 # date-modified: ""
-categories: 
+categories:
   - github actions
   - automation
   - servers
@@ -88,7 +88,7 @@ has to be kept in the `.github/workflows/` folder of the repository and
 the file must be a [YAML](https://en.wikipedia.org/wiki/YAML) file
 (ending in `.yml` or `.yaml`):
 
-```         
+```
 reponame/
 └── .github/
     └── workflows/
@@ -296,7 +296,7 @@ repository, we need to give the workflow some permissions to be able to
 write to that branch. We'll add that by using the `permissions` section:
 
 ``` yaml
-permissions: 
+permissions:
     contents: write
     pages: write
 ```
@@ -356,12 +356,12 @@ second version `v2`). Lastly, we want to run Quarto to build the website
 and publish it to the `gh-pages` branch:
 
 ``` yaml
-      - name: Publish to GitHub Pages (and render) 
+      - name: Publish to GitHub Pages (and render)
         uses: quarto-dev/quarto-actions/publish@v2
         with:
           target: gh-pages
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 ```
 
 Because we will be saving the built website to the `gh-pages` branch, we
@@ -386,7 +386,7 @@ on:
   push:
     branches:
       - main
-permissions: 
+permissions:
     contents: write
     pages: write
 jobs:
@@ -397,12 +397,12 @@ jobs:
         uses: actions/checkout@v4
       - name: Set up Quarto
         uses: quarto-dev/quarto-actions/setup@v2
-      - name: Publish to GitHub Pages (and render) 
+      - name: Publish to GitHub Pages (and render)
         uses: quarto-dev/quarto-actions/publish@v2
         with:
           target: gh-pages
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 ```
 
 With these few lines of code, we now have a GitHub Actions workflow that

learn/shorts/python-packaging-basics.qmd

@@ -6,7 +6,7 @@ description: |
 author: Luke W. Johnston
 date: 2023-07-25
 # date-modified: ""
-categories: 
+categories:
   - python
   - packaging
   - introduction
@@ -70,7 +70,7 @@ files that look a bit like this:
 
 <!-- Created with: https://tree.nathanfriend.io/ -->
 
-```         
+```
 packagename/
 ├── packagename/
 │   ├── ___init___.py

posts/fair-impact-roadshow-dk/index.qmd

@@ -1,7 +1,7 @@
 ---
 title: "Experiences from the FAIR-IMPACT National Roadshow in Denmark"
 description: "An online event to showcase FAIR activities happening across European Union countries."
-author: 
+author:
   - "Luke W. Johnston"
   - "Kristiane Beicher"
 date: "2024-10-28"

posts/github-intro-tvaers-2025/index.qmd

@@ -1,7 +1,7 @@
 ---
 title: "GitHub presentation for Tværs Gruppemøde, April 2025"
 description: "A presentation introducing GitHub and what it can be used for in a research context. Presented at the Tværs Gruppemøde in April 2025."
-author: 
+author:
   - "Signe Kirk Brødbæk"
 date: "2025-04-28"
 categories:

posts/github-intro-tvaers-2025/slides.qmd

@@ -2,7 +2,7 @@
 title: "Introduction to GitHub"
 subtitle: "Tværs Gruppemøde, April 2025"
 author: "Signe Kirk Brødbæk"
-format: 
+format:
     revealjs:
         theme: default
         slide-number: true
@@ -66,7 +66,7 @@ I spend 95 % of my work time using GitHub :raised_hands:
 -   Website: At its core, it's a website. If you open up your browser
     and type in "GitHub.com", you will be taken to GitHub
 -   Stores files: GitHub is a place where you can store and share files
-    related to a project, like a website, in a "repository" (meaning "storage" or "place to keep things", in Danish: "opbevare"). 
+    related to a project, like a website, in a "repository" (meaning "storage" or "place to keep things", in Danish: "opbevare").
     - A repository is like a folder on your computer, but instead of being on your
     computer, it's on the internet. You can access it from anywhere with
     an internet connection.