track_open_instances 0.1.11 → 0.1.12

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3e70a893165f373d3983f0ff446918a4a806908367e729314de68669eb095587
-  data.tar.gz: b0a531423a5494f23c7b1b15983157eaf26f01df4843b1d3abe4a50896dfb93c
+  metadata.gz: ee4204d94143dd1fc33ed919d471780a6555924acbcff72154d762ff11c16263
+  data.tar.gz: a471087b9c689bf1678c0351cc2588b718c20a941f378c08afb8eb398a50fa03
 SHA512:
-  metadata.gz: 78ab8e2bb5ff146622df6a1c0f10f9d40594206300e22f8ee7d598e8db2774df183154e6197ad0727119fadb52e00b0781f7091760bb96453cab1ebb813ad81d
-  data.tar.gz: 96ad69a489b8fca581f44b6bae930d60d360bfc84a4b5fbede31f491535caf97e1173cb725f5adb7cb8edf9e3941341784b6886b83b641e449b1bb5217d39784
+  metadata.gz: e7b27a6315256481f06f4ede6ce7296858b41fd1166c33298a8e3501a7dfd3813dd55404c05b5b32d30246f0fa44bdd97fba34e8806b67d1ce055d854885a696
+  data.tar.gz: 580b7e3c621ba50a9dd5c08c0d8c5fbe653e7f5337846704e927ba1fd956a7ba9d4082100cc05a67440e517776485978ab2489805ee7719719aa3e8e9a684894

data/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.1.11"
+  ".": "0.1.12"
 }

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Change Log
 
+## [0.1.12](https://github.com/main-branch/track_open_instances/compare/v0.1.11...v0.1.12) (2025-04-15)
+
+
+### Bug Fixes
+
+* Change the release PR title to be more user friendly ([0fb9ce2](https://github.com/main-branch/track_open_instances/commit/0fb9ce2cbac10a4efdf44d47bd0cf316d99fc410))
+* Remove pull request title pattern from release configuration ([2460dde](https://github.com/main-branch/track_open_instances/commit/2460ddeabd975b42925daf0572220ef6cbe208fd))
+
 ## [0.1.11](https://github.com/main-branch/track_open_instances/compare/v0.1.10...v0.1.11) (2025-04-15)
 
 

data/CONTRIBUTING.md

@@ -35,6 +35,64 @@ There is three step process for code or documentation changes:
 
 Make your changes in a fork of the track_open_instances repository.
 
+#### Conventional commits
+
+All commits to this repository MUST follow [the conventional commits
+specification](https://www.conventionalcommits.org/en/v1.0.0/#specification). This is
+so that release versions can automatically be generated based on the commit messages.
+The Continuous Integration workflow will fail if a commit message is not in this
+format.
+
+The format for a conventional commit message is:
+
+```Text
+<commit-type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+Where commit type is one of:
+
+* `feat:` A new feature for the end-user.
+* `fix:` A bug fix for the end-user.
+* `build:` Changes that affect the build system or external dependencies (e.g.,
+  changes to npm, webpack, Docker configurations).
+* `chore:` Routine tasks, maintenance, or changes that don't modify source code or
+  test files (e.g., updating dependencies, configuring linters).
+* `docs:` Changes to documentation only (e.g., updating README, guides, or extensive
+  code comments).
+* `style:` Changes that do not affect the meaning or logic of the code (e.g.,
+  white-space, formatting, fixing linter warnings, missing semi-colons).
+* `refactor:` A code change that neither fixes a bug nor adds a feature, but improves
+  the code structure, readability, or organization without changing its external
+  behavior.
+* `perf:` A code change that improves performance.
+* `test:` Adding missing tests or correcting existing tests; changes to the test
+  environment or configuration.
+
+Backward incompatible changes (aka breaking changes) should append a `!` after the
+commit type or add the footer `BREAKING CHANGE:` as shown in the following examples:
+
+```Text
+fix!: change the interface to match the requirements
+```
+
+```Text
+fix: change the interface to match the requirements
+
+BREAKING CHANGE: users will need to add additional, non-default option
+```
+
+These commit messages will have the following impact on the release version number:
+
+* Breaking changes (of any commit type) will bump the major version component
+* `feat:` commits will bump the minor version component
+* `fix:` commits will bump the patch version component
+
+Any other commit types (that are not breaking changes) will not trigger a release.
+
 ### Create a pull request
 
 See [this article](https://help.github.com/articles/about-pull-requests/) if you
@@ -62,12 +120,38 @@ request meets [the project's coding standards](#coding-standards).
 
 All pull requests must meet these requirements:
 
-### 1 PR = 1 Commit
-
-- All commits for a PR must be squashed into one commit
-- To avoid an extra merge commit, the PR must be able to be merged as [a fast forward merge](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging)
-- The easiest way to ensure a fast forward merge is to rebase your local branch
-  to the track_open_instances main branch
+### Rebase Merge Strategy
+
+Our project requires a linear commit history, which is achieved by using a
+rebase strategy to enable fast-forward merges for all Pull Requests (PRs).
+
+* **Goal:** To integrate PRs without creating extra merge commits, ensuring a clean
+  and linear project history. This requires the PR branch to be eligible for a
+  [fast-forward
+  merge](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging).
+* **Commit History:** Before merging, clean up your PR's commit history. Squash
+  related changes into logical commits using interactive rebase (`git rebase -i`).
+  Aim for a minimal number of meaningful commits that represent distinct steps or
+  features.
+* **Enable Fast-Forward:** To ensure a fast-forward merge is possible, you must
+  rebase your feature branch onto the latest version of the target branch (e.g.,
+  `main`) *before* the PR is merged.
+  * Example commands (assuming your remote is `origin` and the target branch is
+    `main`):
+
+    ```bash
+    # Fetch the latest changes from the remote
+    git fetch origin
+
+    # Rebase your current branch onto the latest main branch
+    git rebase origin/main
+    ```
+
+  * You may need to resolve conflicts during the rebase process. After successfully
+    rebasing, you'll likely need to force-push your branch (`git push
+    --force-with-lease`).
+
+  * You may need to rebase again if other PRs are merged to main.
 
 ### Unit tests
 

data/lib/track_open_instances/version.rb

@@ -2,5 +2,5 @@
 
 module TrackOpenInstances
   # The last released version of this gem
-  VERSION = '0.1.11'
+  VERSION = '0.1.12'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: track_open_instances
 version: !ruby/object:Gem::Version
-  version: 0.1.11
+  version: 0.1.12
 platform: ruby
 authors:
 - James Couball
@@ -218,8 +218,8 @@ metadata:
   allowed_push_host: https://rubygems.org
   homepage_uri: https://github.com/main-branch/track_open_instances
   source_code_uri: https://github.com/main-branch/track_open_instances
-  documentation_uri: https://rubydoc.info/gems/track_open_instances/0.1.11
-  changelog_uri: https://rubydoc.info/gems/track_open_instances/0.1.11/file/CHANGELOG.md
+  documentation_uri: https://rubydoc.info/gems/track_open_instances/0.1.12
+  changelog_uri: https://rubydoc.info/gems/track_open_instances/0.1.12/file/CHANGELOG.md
   rubygems_mfa_required: 'true'
 rdoc_options: []
 require_paths: