chore(branding): migration to the litestar-org (#156)

.github/CODEOWNERS

@@ -1,7 +1,7 @@
-# Code owner settings for `jolt-org`
+# Code owner settings for `litestar-org`
 # @maintainers should be assigned to all reviews.
 # Most specific assignment takes precedence though, so if you add a more specific thing than the `*` glob, you must also add @maintainers
 # For more info about code owners see https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#codeowners-file-example
 
 # Global Assignment
-*      @jolt-org/maintainers @jolt-org/members
+*      @litestar-org/maintainers @litestar-org/members

.github/workflows/ci.yaml

@@ -43,7 +43,7 @@ jobs:
     needs:
       - test
       - validate
-    if: github.event.pull_request.head.repo.fork == false && github.repository_owner == 'jolt-org'
+    if: github.event.pull_request.head.repo.fork == false && github.repository_owner == 'litestar-org'
     runs-on: ubuntu-latest
     steps:
       - name: Check out repository

.github/workflows/docs-preview.yaml

@@ -33,7 +33,7 @@ jobs:
         with:
           folder: docs-preview/docs/_build/html
           token: ${{ secrets.DOCS_PREVIEW_DEPLOY_TOKEN }}
-          repository-name: jolt-org/advanced-alchemy-docs-preview
+          repository-name: litestar-org/advanced-alchemy-docs-preview
           clean: false
           target-folder: ${{ env.PR_NUMBER }}
           branch: gh-pages
@@ -44,7 +44,7 @@ jobs:
         with:
           script: |
             const issue_number = process.env.PR_NUMBER
-            const body = "Documentation preview will be available shortly at https://jolt-org.github.io/advanced-alchemy-docs-preview/" + issue_number
+            const body = "Documentation preview will be available shortly at https://litestar-org.github.io/advanced-alchemy-docs-preview/" + issue_number
 
             const opts = github.rest.issues.listComments.endpoint.merge({
               owner: context.repo.owner,

CODEOWNERS

@@ -1,7 +1,7 @@
-# Code owner settings for `jolt-org`
+# Code owner settings for `litestar-org`
 # @maintainers should be assigned to all reviews.
 # Most specific assignment takes precedence though, so if you add a more specific thing than the `*` glob, you must also add @maintainers
 # For more info about code owners see https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#codeowners-file-example
 
 # Global Assignment
-*      @jolt-org/maintainers @jolt-org/members
+*      @litestar-org/maintainers @litestar-org/members

CONTRIBUTING.rst

@@ -17,7 +17,7 @@ Code contributions
 Workflow
 ++++++++
 
-1. `Fork <https://github.com/jolt-org/advanced-alchemy/fork>`_ the `Advanced Alchemy repository <https://github.com/jolt-org/advanced-alchemy>`_
+1. `Fork <https://github.com/litestar-org/advanced-alchemy/fork>`_ the `Advanced Alchemy repository <https://github.com/litestar-org/advanced-alchemy>`_
 2. Clone your fork locally with git
 3. `Set up the environment <#setting-up-the-environment>`_
 4. Make your changes
@@ -68,13 +68,13 @@ Then you can serve the documentation with ``make docs-serve``, or build them wit
 Creating a new release
 ----------------------
 
-1. Increment the version in `pyproject.toml <https://github.com/jolt-org/advanced-alchemy/blob/main/pyproject.toml>`_.
+1. Increment the version in `pyproject.toml <https://github.com/litestar-org/advanced-alchemy/blob/main/pyproject.toml>`_.
     .. note:: The version should follow `semantic versioning <https://semver.org/>`_ and `PEP 440 <https://www.python.org/dev/peps/pep-0440/>`_.
-2. `Draft a new release <https://github.com/jolt-org/advanced-alchemy/releases/new>`_ on GitHub
+2. `Draft a new release <https://github.com/litestar-org/advanced-alchemy/releases/new>`_ on GitHub
 
    * Use ``vMAJOR.MINOR.PATCH`` (e.g. ``v1.2.3``) as both the tag and release title
    * Fill in the release description. You can use the "Generate release notes" function to get a draft for this
 3. Commit your changes and push to ``main``
 4. Publish the release
-5. Go to `Actions <https://github.com/jolt-org/advanced-alchemy/actions>`_ and approve the release workflow
+5. Go to `Actions <https://github.com/litestar-org/advanced-alchemy/actions>`_ and approve the release workflow
 6. Check that the workflow runs successfully

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2023 Jolt
+Copyright (c) 2024 Litestar Organization
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

Makefile

@@ -61,6 +61,14 @@ clean: 												## Cleanup temporary build artifacts
 destroy: 											## Destroy the virtual environment
 	@rm -rf .venv
 
+.PHONY: refresh-lockfiles
+refresh-lockfiles:                                 ## Sync lockfiles with requirements files.
+	pdm update --update-reuse --group :all
+
+.PHONY: lock
+lock:                                             ## Rebuild lockfiles from scratch, updating all dependencies
+	pdm update --update-eager --group :all
+
 # =============================================================================
 # Tests, Linting, Coverage
 # =============================================================================