change to hugo-blog-awesome theme

This commit is contained in:
Colmaris 2025-03-21 15:51:55 +01:00
parent 113e3650f1
commit 15b6142a8e
131 changed files with 5895 additions and 124 deletions

View file

@ -0,0 +1,12 @@
# These are supported funding model platforms
# github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
# patreon: # Replace with a single Patreon username
# open_collective: # Replace with a single Open Collective username
ko_fi: sidharth
# tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
# community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
# liberapay: # Replace with a single Liberapay username
# issuehunt: # Replace with a single IssueHunt username
# otechie: # Replace with a single Otechie username
# lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry

View file

@ -0,0 +1,32 @@
---
name: Bug report
about: Report a bug to help us improve.
title: ''
labels: ''
assignees: ''
---
**Describe the bug**
A clear and concise description of what the bug is.
**Steps to reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Device information**
- OS: [e.g. iOS]
- Browser [e.g. firefox, safari]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.

View file

@ -0,0 +1,8 @@
blank_issues_enabled: false
contact_links:
- name: Questions or support
url: https://github.com/hugo-sid/hugo-blog-awesome/discussions/
about: Please use GitHub discussions to ask and answer questions.
- name: Feature request
url: https://github.com/hugo-sid/hugo-blog-awesome/discussions/categories/feature-requests
about: Please use the feature requests section in GitHub discussions to propose new features or ideas.

View file

@ -0,0 +1,7 @@
---
name: New blank issue
about: Use this to mention anything other than bug report.
title: ""
labels: ""
assignees: ""
---

View file

@ -0,0 +1,39 @@
<!--
## Read this before opening a PR.
Thank you for contributing to hugo-blog-awesome!
Please fill out the following questions to make it easier for us to review your
changes. Neither you need to answer all questions nor you have to check all the boxes below.
-->
## What problem does this PR solve?
<!--
A small description of the fix.
-->
## Is this PR adding a new feature?
<!--
A small description of the feature.
-->
## Is this PR related to any issue or discussion?
<!--
Provide link(s) to any relevant issue or discussion post here.
If this PR resolves an existing issue (say issue number 1), write "Closes #1" in your pull request description (not in title) so that the issue is closed automatically when this PR is merged.
-->
## PR Checklist
- [ ] I have verified that the code works as described/as intended.
- [ ] This change adds a social icon which has a permissive license to use it.
- [ ] This change **does not** include any external library/resources.
- [ ] This change **does not** include any unrelated scripts (e.g. bash and python scripts).
- [ ] I have enabled [maintainer edits for this PR](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork).

View file

@ -0,0 +1,49 @@
name: "Pull Request auto-label"
on:
# Including 'on push' trigger, so that PRs touching the same files as push are checked for conflicts.
# PR can be rebased (against main brnach) to resolve conflicts.
push:
branches: [ main ]
pull_request_target:
types: [ opened, synchronize ]
jobs:
conflicts:
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: write
steps:
- name: Update PRs with conflict labels
uses: eps1lon/actions-label-merge-conflict@657e437ea2533fd743739be26f0a2eeb420b306a # releases/2.1.0
with:
dirtyLabel: "conflicts"
#removeOnDirtyLabel: "PR: ready to ship"
repoToken: "${{ secrets.GITHUB_TOKEN }}"
commentOnDirty: "This pull request has conflicts with the base branch, please resolve those so that we can review the pull request."
commentOnClean: "Conflicts have been resolved! 🎉 A maintainer will soon review the pull request."
size:
if: github.event_name == 'pull_request' || github.event_name == 'pull_request_target'
permissions:
issues: write
pull-requests: write
runs-on: ubuntu-latest
steps:
- uses: codelytv/pr-size-labeler@1c3422395d899286d5ee2c809fd5aed264d5eb9b # v1.10.2
with:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
xs_label: 'size/xs'
xs_max_size: 35
s_label: 'size/s'
s_max_size: 75
m_label: 'size/m'
m_max_size: 150
l_label: 'size/l'
l_max_size: 300
xl_label: 'size/xl'
message_if_xl: >
This PR exceeds the recommended size of 300 lines (counting both additions & deletions).
Kindly ensure that you are NOT addressing multiple issues in one PR.
We recommend you to create atomic PRs which focus on a single change.

View file

@ -0,0 +1,21 @@
on:
push:
branches:
- main
permissions:
contents: write
pull-requests: write
name: Create release PR
jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: google-github-actions/release-please-action@db8f2c60ee802b3748b512940dde88eabd7b7e01 # v3.7.13
with:
release-type: simple
token: ${{ secrets.HBA_RELEASE_PLEASE_TOKEN }}
pull-request-header: ":rocket: New release"
changelog-types: '[{"type":"feat","section":":sparkles: Features","hidden":false},{"type":"fix","section":":bug: Bug Fixes","hidden":false},{"type":"chore","section":":hammer: Housekeeping","hidden":false},{"type":"docs","section":":memo: Documentation","hidden":false},{"type":"ci","section":":construction_worker: CI/CD","hidden":false},{"type":"perf","section":":zap: Performance","hidden":false},{"type":"refactor","section":":recycle: Refactoring","hidden":false},{"type":"style","section":":art: Style","hidden":false},{"type":"test","section":":white_check_mark: Tests","hidden":false}]'

View file

@ -0,0 +1,72 @@
# This workflow uses actions that are not certified by GitHub. They are provided
# by a third-party and are governed by separate terms of service, privacy
# policy, and support documentation.
name: Scorecard supply-chain security
on:
# For Branch-Protection check. Only the default branch is supported. See
# https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection
branch_protection_rule:
# To guarantee Maintained check is occasionally updated. See
# https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained
schedule:
- cron: '25 10 * * 3'
push:
branches: [ "main" ]
# Declare default permissions as read only.
permissions: read-all
jobs:
analysis:
name: Scorecard analysis
runs-on: ubuntu-latest
permissions:
# Needed to upload the results to code-scanning dashboard.
security-events: write
# Needed to publish results and get a badge (see publish_results below).
id-token: write
# Uncomment the permissions below if installing in a private repository.
# contents: read
# actions: read
steps:
- name: "Checkout code"
uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
with:
persist-credentials: false
- name: "Run analysis"
uses: ossf/scorecard-action@62b2cac7ed8198b15735ed49ab1e5cf35480ba46 # v2.4.0
with:
results_file: results.sarif
results_format: sarif
# (Optional) "write" PAT token. Uncomment the `repo_token` line below if:
# - you want to enable the Branch-Protection check on a *public* repository, or
# - you are installing Scorecard on a *private* repository
# To create the PAT, follow the steps in https://github.com/ossf/scorecard-action#authentication-with-pat.
# repo_token: ${{ secrets.SCORECARD_TOKEN }}
# Public repositories:
# - Publish results to OpenSSF REST API for easy access by consumers
# - Allows the repository to include the Scorecard badge.
# - See https://github.com/ossf/scorecard-action#publishing-results.
# For private repositories:
# - `publish_results` will always be set to `false`, regardless
# of the value entered here.
publish_results: true
# Upload the results as artifacts (optional). Commenting out will disable uploads of run results in SARIF
# format to the repository Actions tab.
- name: "Upload artifact"
uses: actions/upload-artifact@6f51ac03b9356f520e9adb1b1b7802705f340c2b # v4.5.0
with:
name: SARIF file
path: results.sarif
retention-days: 5
# Upload the results to GitHub's code scanning dashboard.
- name: "Upload to code-scanning"
uses: github/codeql-action/upload-sarif@461ef6c76dfe95d5c364de2f431ddbd31a417628 # v3.26.9
with:
sarif_file: results.sarif

View file

@ -0,0 +1,30 @@
# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
#
# You can adjust the behavior by modifying this file.
# For more information, see:
# https://github.com/actions/stale
name: Mark stale issues and pull requests
on: workflow_dispatch
jobs:
stale:
runs-on: ubuntu-latest
permissions:
issues: write
pull-requests: write
steps:
- uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e # v9.0.0
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
days-before-issue-stale: 21
days-before-pr-stale: 21
days-before-close: 7
stale-issue-message: 'This issue has been marked stale due to inactivity. It will auto-close in 7 days without an update.'
close-issue-message: 'This issue was auto-closed due to inactivity.'
stale-pr-message: 'This pull request has been marked stale due to inactivity. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update.'
close-pr-message: 'This pull request was auto-closed due to inactivity.'
exempt-all-assignees: true
exempt-issue-labels: accepted