Release/1.0.0 beta.2

.github/actions/gwy/badges/action.yml

@@ -485,9 +485,10 @@ runs:
         echo "**Issues:**" >> $GITHUB_STEP_SUMMARY
         echo "" >> $GITHUB_STEP_SUMMARY
 
-        ISSUES=$(curl -s -H "Authorization: Bearer ${{ inputs.token }}" \
-          "https://api.github.com/repos/${GITHUB_REPOSITORY}/issues?state=open" | jq -r 'length')
-
+        ISSUES=$(curl -s -H "Accept: application/vnd.github+json" -H "Authorization: Bearer ${{ inputs.token }}" \
+          "https://api.github.com/search/issues?q=repo:${GITHUB_REPOSITORY}+is:issue+state:open" \
+          | jq .total_count)
+
         if [ -n "$ISSUES" ]; then
           SAVE_FAILED=false
           for STYLE in flat flat-square plastic for-the-badge; do

.github/workflows/gwy-badges.yml

@@ -100,6 +100,7 @@ env:
 on:
   push:
     branches:
+      - main
       - master
 
   workflow_dispatch:

CHANGELOG.md

@@ -5,6 +5,24 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.0-beta.2] - 2025-05-18
+
+This is the first official release beta.
+
+The project has been [extensively tested](https://github.com/earcamone/gwy-playground/actions)
+but because, at the end of the day, it's a sole programmer project, I'm leaving
+some space for possible bugs reporting so, if you find some, kindly report them.
+
+### Added
+
+- Badges Generation Workflow: added trigger on release 
+  pushes event to additional "master" branch `main`
+
+### Fixed
+
+- Badges Generation Workflow: Fixed bug in "Issues" count badge,
+  it was summing together opened issues and pull requests.
+
 ## [1.0.0-beta.1] - 2025-05-16
 
 This is the first official release beta. 

README.md

@@ -553,6 +553,19 @@ them in your documentation, getting updated automatically in your next
 release. You can also schedule a daily job to run the workflow, updating
 automatically all your count badges like `Downloads` and `Stars`.
 
+By default, this workflow gets triggered automatically on push events to 
+popular "master" branches `master` and `main`. If you happen to have a 
+different one, you can customize your releases master branch name by editing 
+the following block inside the workflow file:
+
+```
+on:
+  push:
+    branches:
+      - main
+      - master
+```
+
 Configure the badges target branch, the target directory within it and which
 of the available GitHub domains you want the urls to be generated with editing 
 the variables at the top of the workflow `.github/workflows/gwy-badges.yml`,