fix(ci): fix renamed branch s/master/main (#184)

Author: crccheck

.github/workflows/ci.yml

@@ -4,7 +4,7 @@ on:
   pull_request:
   push:
     branches:
-      - master
+      - main
 
 jobs:
   prepare:

.github/workflows/conventional-pr.yml

@@ -6,7 +6,7 @@ on:
       - edited
       - synchronize
     branches:
-      - master
+      - main
 jobs:
   lint-pr:
     runs-on: ubuntu-latest

.github/workflows/release.yml

@@ -6,7 +6,7 @@ on:
   # Disabled to be able to roll multiple breaking releases into one release
   # push:
   #   branches:
-  #     - master
+  #     - main
 
 jobs:
   release:
@@ -25,7 +25,7 @@ jobs:
       - name: Setup | Force release branch to be at workflow sha
         run: |
           git reset --hard ${{ github.sha }}
-      - name: Python Semantic Release
+      - name: Action | Python Semantic Release
         id: release
         # https://github.com/python-semantic-release/python-semantic-release/releases
         # https://python-semantic-release.readthedocs.io/en/latest/github-action.html

README.md

@@ -1,6 +1,6 @@
 # Django Object Actions
 
-[![CI](https://github.com/crccheck/django-object-actions/actions/workflows/ci.yml/badge.svg?branch=master)](https://github.com/crccheck/django-object-actions/actions/workflows/ci.yml?query=branch%3Amaster)
+[![CI](https://github.com/crccheck/django-object-actions/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/crccheck/django-object-actions/actions/workflows/ci.yml?query=branch%3Amain)
 
 If you've ever tried making admin object tools you may have thought, "why can't
 this be as easy as making Django Admin Actions?" Well now they can be.