django-clerk-users 0.1.3__tar.gz → 0.1.4__tar.gz

django_clerk_users-0.1.4/.claude/skills/gh-issues/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: gh-issues
+description: Review open GitHub issues and start working on one. Lists issues, shows details, creates a branch, and sets up todos.
+argument-hint: "[issue-number]"
+---
+
+# GitHub Issues Skill
+
+Help the user review and start working on GitHub issues from the current repository.
+
+## Workflow
+
+### Step 1: List Open Issues
+
+If no issue number was provided as an argument, list open issues:
+
+```bash
+gh issue list --state open --limit 20
+```
+
+Present the issues in a clear format and ask the user which one they'd like to work on using AskUserQuestion. Include issue number, title, and labels.
+
+### Step 2: Get Issue Details
+
+Once an issue is selected (either from argument or user selection), fetch the full details:
+
+```bash
+gh issue view <issue-number>
+```
+
+Display:
+- Title and description
+- Labels and assignees
+- Any linked PRs or related issues
+- Comments (if relevant)
+
+### Step 3: Create a Working Branch
+
+Always create a new branch for this issue:
+
+```bash
+git checkout -b <branch-name>
+```
+
+Suggest a branch name based on the issue (e.g., `fix/123-brief-description` or `feat/123-brief-description`).
+
+### Step 4: Create Todo List
+
+Based on the issue description and any acceptance criteria, use TodoWrite to create a structured task list. Break down the work into:
+- Investigation/research tasks (if needed)
+- Implementation tasks
+- Testing tasks
+- Documentation updates (if needed)
+
+### Step 5: Start Working
+
+Begin working on the first todo item. Use the codebase exploration tools to understand the relevant code before making changes.
+
+## Important Notes
+
+- Always check `git status` before creating a branch to ensure clean working state
+- If the issue is unclear, ask clarifying questions before starting work
+- Reference the issue number in commit messages (e.g., "Fix #123: description")
+- Keep the user informed of progress by updating todos as you work

django_clerk_users-0.1.4/.claude/skills/release/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: release
+description: Release a new version by bumping version, tagging, and pushing to GitHub.
+argument-hint: "[patch|minor|major|X.Y.Z]"
+---
+
+# Release Skill
+
+Release a new version of this Copier template to GitHub.
+
+## Arguments (optional)
+
+- `$ARGUMENTS` - Bump type: `patch` (default), `minor`, or `major`. Or a specific version like `0.5.0`.
+
+## Steps
+
+1. Get the current version from the latest git tag:
+   ```bash
+   git describe --tags --abbrev=0
+   ```
+
+2. Determine the new version:
+   - If no argument or `patch`: increment patch (0.2.4 -> 0.2.5)
+   - If `minor`: increment minor, reset patch (0.2.4 -> 0.3.0)
+   - If `major`: increment major, reset minor and patch (0.2.4 -> 1.0.0)
+   - If specific version provided (X.Y.Z format): use that version
+
+3. Confirm the version bump with the user using AskUserQuestion:
+   - Show current version and new version
+   - Ask for confirmation before proceeding
+
+4. Create a git tag: `v{version}`
+   ```bash
+   git tag v{version}
+   ```
+
+5. Push the tag to origin:
+   ```bash
+   git push origin v{version}
+   ```
+
+6. Report success with the new version number and a link to the GitHub releases page.
+
+## Important
+
+- Do NOT include a co-authored-by line in commits
+- The version should be in format `X.Y.Z` (e.g., `0.2.5`)
+- Tags should be prefixed with `v` (e.g., `v0.2.5`)
+- This template uses git tags as the version source (no version file to update)
+- Ensure working directory is clean before tagging

{django_clerk_users-0.1.3 → django_clerk_users-0.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: django-clerk-users
-Version: 0.1.3
+Version: 0.1.4
 Summary: Integrate Clerk with Django
 Project-URL: Changelog, https://github.com/jmitchel3/django-clerk-users
 Project-URL: Documentation, https://github.com/jmitchel3/django-clerk-users

{django_clerk_users-0.1.3 → django_clerk_users-0.1.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "django-clerk-users"
-version = "0.1.3"
+version = "0.1.4"
 description = "Integrate Clerk with Django"
 readme = "README.md"
 requires-python = ">=3.12"

django_clerk_users-0.1.4/src/django_clerk_users/admin.py

@@ -0,0 +1,64 @@
+"""
+Django admin configuration for ClerkUser model.
+"""
+
+from django.contrib import admin
+from django.contrib.auth.admin import UserAdmin
+
+from django_clerk_users.models import ClerkUser
+
+
+@admin.register(ClerkUser)
+class ClerkUserAdmin(UserAdmin):
+    list_display = [
+        "email",
+        "first_name",
+        "last_name",
+        "clerk_id",
+        "is_staff",
+        "is_active",
+    ]
+    list_filter = ["is_staff", "is_active", "created_at"]
+    search_fields = ["email", "first_name", "last_name", "clerk_id"]
+    ordering = ["-created_at"]
+
+    fieldsets = (
+        (None, {"fields": ("email", "password")}),
+        ("Personal info", {"fields": ("first_name", "last_name", "image_url")}),
+        ("Clerk", {"fields": ("clerk_id", "uid")}),
+        (
+            "Permissions",
+            {
+                "fields": (
+                    "is_active",
+                    "is_staff",
+                    "is_superuser",
+                    "groups",
+                    "user_permissions",
+                )
+            },
+        ),
+        (
+            "Timestamps",
+            {"fields": ("created_at", "updated_at", "last_login", "last_logout")},
+        ),
+    )
+
+    add_fieldsets = (
+        (
+            None,
+            {
+                "classes": ("wide",),
+                "fields": ("email", "password1", "password2"),
+            },
+        ),
+    )
+
+    readonly_fields = [
+        "uid",
+        "clerk_id",
+        "created_at",
+        "updated_at",
+        "last_login",
+        "last_logout",
+    ]