chore: clean up CI config, contributing docs, and PR template

## What

Simplify the release workflow trigger condition by collapsing redundant
label checks, add Docker ecosystem to Dependabot monitoring, rewrite
CONTRIBUTING.md with structured guidance, and add a pull request template.

## Why

The release workflow condition enumerated every combination of the
release label with major/minor/patch, which was logically equivalent to
just checking for the release label. The contributing guide needed
modernization with clearer sections for bug reports, enhancements, and
PR standards.

## Notes

- The simplified release condition is functionally identical — major/minor/patch labels alone still do NOT trigger a release
- CONTRIBUTING.md now references GitHub Issues templates (bug_report.yml, feature_request.yml) that should exist in .github/ISSUE_TEMPLATE/

Signed-off-by: jmeridth <jmeridth@gmail.com>

Author: jmeridth

.github/dependabot.yaml

@@ -1,10 +1,10 @@
 version: 2
 updates:
-  - package-ecosystem: 'github-actions'
-    directory: '/'
+  - package-ecosystem: "github-actions"
+    directory: "/"
     schedule:
-      interval: 'daily'
-      timezone: 'America/Chicago'
+      interval: "daily"
+      timezone: "America/Chicago"
     commit-message:
       prefix: "chore(deps)"
     labels: ["github_actions", "dependencies"]
@@ -14,3 +14,17 @@ updates:
         update-types:
           - "minor"
           - "patch"
+  - package-ecosystem: "docker"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    cooldown:
+      default-days: 7
+    commit-message:
+      prefix: "chore(deps)"
+    labels: ["docker", "dependencies"]
+    groups:
+      dependencies:
+        applies-to: version-updates
+        update-types:
+          - "minor"

.github/pull_request_template.md

@@ -0,0 +1,20 @@
+# Pull Request
+
+<!--
+PR title needs to be prefixed with a conventional commit type
+(build,chore,ci,docs,feat,fix,perf,refactor,revert,style,test)
+
+It should also be brief and descriptive for a good changelog entry
+
+examples: "feat: add new logger" or "fix: remove unused imports"
+-->
+
+## Proposed Changes
+
+<!-- Describe what the changes are and link to a GitHub Issue if one exists -->
+
+## Readiness Checklist
+
+### Author/Contributor
+
+- [ ] If documentation is needed for this change, has that been included in this pull request

.github/workflows/release.yaml

@@ -25,42 +25,17 @@ on:
         value: ${{ jobs.create_release.outputs.body }}
 jobs:
   create_release:
-    # release if:
-    # Manual deployment (workflow_dispatch) OR
-    # The pull request was merged AND
-    # It has at least one of these:
-    #  - reaking
-    #  - feature
-    #  - vuln
-    #  - release (with or without any of major / minor / patch labels)
-    if: |
-      (
-      github.event_name == 'workflow_dispatch') ||
+    # Release if:
+    # - Manual deployment (workflow_dispatch), OR
+    # - PR was merged with a breaking, feature, vuln, or release label
+    # Note: major/minor/patch labels alone do NOT trigger a release
+    if: >
+      github.event_name == 'workflow_dispatch' ||
       (github.event.pull_request.merged == true &&
-      ((
-      contains(github.event.pull_request.labels.*.name, 'breaking') ||
-      contains(github.event.pull_request.labels.*.name, 'feature') ||
-      contains(github.event.pull_request.labels.*.name, 'vuln')
-      ) ||
-      (
-      contains(github.event.pull_request.labels.*.name, 'release') &&
-      !(
-        contains(github.event.pull_request.labels.*.name, 'major') ||
-        contains(github.event.pull_request.labels.*.name, 'minor') ||
-        contains(github.event.pull_request.labels.*.name, 'patch')
-      )) ||
-      (
-      contains(github.event.pull_request.labels.*.name, 'release') &&
-      contains(github.event.pull_request.labels.*.name, 'major')
-      ) ||
-      (
-      contains(github.event.pull_request.labels.*.name, 'release') &&
-      contains(github.event.pull_request.labels.*.name, 'minor')
-      ) ||
-      (
-      contains(github.event.pull_request.labels.*.name, 'release') &&
-      contains(github.event.pull_request.labels.*.name, 'patch')
-      )))
+       (contains(github.event.pull_request.labels.*.name, 'breaking') ||
+        contains(github.event.pull_request.labels.*.name, 'feature') ||
+        contains(github.event.pull_request.labels.*.name, 'vuln') ||
+        contains(github.event.pull_request.labels.*.name, 'release')))
     outputs:
       full-tag: ${{ steps.release-drafter.outputs.tag_name }}
       short-tag: ${{ steps.get_tag_name.outputs.SHORT_TAG }}

CONTRIBUTING.md

@@ -1,33 +1,83 @@
-## Contributing
+<!-- markdownlint-disable MD013 -->
+<!-- omit in toc -->
 
-[fork]: https://github.com/github-community-projects/ospo-reusable-workflows/fork
-[pr]: https://github.com/github-community-projects/ospo-reusable-workflows/compare
+# Contributing to ospo-reusable-workflows
 
-Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
+First off, thanks for taking the time to contribute! :heart:
 
-Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE).
+All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us project owners and smooth out the experience for all involved. The team looks forward to your contributions. :tada:
 
-Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
+<!-- omit in toc -->
 
-## Submitting a pull request
+## Table of Contents
 
-1. [Fork][fork] and clone the repository
-1. Configure and install the dependencies: `script/bootstrap`
-1. Make sure the tests pass on your machine: `rake`
-1. Create a new branch: `git checkout -b my-branch-name`
-1. Make your change, add tests, and make sure the tests still pass
-1. Push to your fork and [submit a pull request][pr]
-1. Pat yourself on the back and wait for your pull request to be reviewed and merged.
+- [I Have a Question](#i-have-a-question)
+- [I Want To Contribute](#i-want-to-contribute)
+- [Reporting Bugs](#reporting-bugs)
+- [Suggesting Enhancements](#suggesting-enhancements)
+- [Releases](#releases)
 
-Here are a few things you can do that will increase the likelihood of your pull request being accepted:
+## I Have a Question
 
-- Follow the [style guide][style].
-- Write tests.
-- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
-- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+Before you ask a question, it is best to search for existing [Issues](https://github.com/github-community-projects/ospo-reusable-workflows/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue.
 
-## Resources
+If you then still feel the need to ask a question and need clarification, we recommend the following:
 
-- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
-- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
-- [GitHub Help](https://help.github.com)
+- Open an [Issue](https://github.com/github-community-projects/ospo-reusable-workflows/issues/new).
+- Provide as much context as you can about what you're running into.
+- Provide project and platform versions (Node.js, npm, etc), depending on what seems relevant.
+
+We will then take care of the issue as soon as possible.
+
+## I Want To Contribute
+
+### Legal Notice <!-- omit in toc -->
+
+When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
+
+## Reporting Bugs
+
+<!-- omit in toc -->
+
+### Before Submitting a Bug Report
+
+A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
+
+- Make sure that you are using the latest version.
+- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the documentation. If you are looking for support, you might want to check [this section](#i-have-a-question)).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/github-community-projects/ospo-reusable-workflows/issues).
+- Collect information about the bug:
+  - Stack trace (Traceback)
+  - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
+  - Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
+  - Possibly your input and the output
+- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
+
+<!-- omit in toc -->
+
+### How Do I Submit a Good Bug Report?
+
+Please submit a bug report using our [GitHub Issues template](https://github.com/github-community-projects/ospo-reusable-workflows/issues/new?template=bug_report.yml).
+
+## Suggesting Enhancements
+
+This section guides you through submitting an enhancement suggestion for ospo-reusable-workflows, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
+
+<!-- omit in toc -->
+
+### Before Submitting an Enhancement
+
+- Make sure that you are using the latest version.
+- Read the documentation carefully and find out if the functionality is already covered, maybe by an individual configuration.
+- Perform a [search](https://github.com/github-community-projects/ospo-reusable-workflows/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature or to develop the feature yourself and contribute it to the project.
+
+<!-- omit in toc -->
+
+### How Do I Submit a Good Enhancement Suggestion?
+
+Please submit an enhancement suggestion using our [GitHub Issues template](https://github.com/github-community-projects/ospo-reusable-workflows/issues/new?template=feature_request.yml).
+
+### Pull Request Standards
+
+We are using [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) to standardize our pull request titles. This allows us to automatically generate labels and changelogs and follow semantic versioning. Please follow the commit message format when creating a pull request. What pull request title prefixes are expected are in the [pull_request_template.md](.github/pull_request_template.md) that is shown when creating a pull request.