refactor: Rename commit-to-git workflow (#5)

Author: anaiberta

.github/workflows/commit-to-git.yml renamed to .github/workflows/update-genexus-dep-version.yml

@@ -1,4 +1,4 @@
-name: Commit to GeneXus repository
+name: Update specified dependency version in GeneXus
 
 on:
     workflow_call:

README.md

@@ -9,7 +9,7 @@ This repository contains a collection of reusable workflows used by different Ge
 - [Repository Content](#repository-content)
 - [Workflows](#workflows)
   - [run-beta-bot](#run-beta-bot)
-  - [commit-to-git](#commit-to-git)
+  - [update-genexus-dep-version](#update-genexus-dep-version)
 - [Contributing](#contributing)
 - [License](#license)
 
@@ -53,11 +53,11 @@ The [run-beta-bot](.github/workflows/run-beta-bot.yml) workflow is used to handl
 
 To use the run-beta-bot workflow, look at the instructions defined in the template workflow [templates/call-beta-bot.yml](templates/call-beta-bot.yml).
 
-### commit-to-git
+### update-genexus-dep-version
 
-The [commit-to-git](.github/workflows/commit-to-git.yml) workflow is used to update the version of a component in the GeneXus source code repository. This workflow automates the process of synchronizing the component version across multiple projects, ensuring consistency and reducing the chance of errors.
+The [update-genexus-dep-version](.github/workflows/update-genexus-dep-version.yml) workflow is used to update the version of a component in the GeneXus source code repository. This workflow automates the process of synchronizing the component version across multiple projects, ensuring consistency and reducing the chance of errors.
 
-To use the commit-to-git workflow, follow the instructions provided in the [templates/call-commit-to-git.yml](templates/call-commit-to-git.yml).
+To use the update-genexus-dep-version workflow, follow the instructions provided in the [templates/call-update-genexus-dep-version.yml](templates/call-update-genexus-dep-version.yml).
 
 ## Contributing
 

templates/call-commit-to-git.yml renamed to templates/call-update-genexus-dep-version.yml

@@ -12,7 +12,7 @@
 # 4. Configure update-genexus-dependency job to execute after your build job and
 #    retrieve the package name and version information.
 # -----------------
-name: Call Commit to Git Workflow
+name: Call "Update GeneXus Dependency Version" Workflow
 
   jobs:
 
@@ -61,12 +61,15 @@ name: Call Commit to Git Workflow
           echo "PACKAGES_NAME=$packageNames" >> $env:GITHUB_OUTPUT
 
 # -- Copy & Paste the following job ---
-  update-genexus-dependency:
-    # Replace the 'buildJob' name in the following lines for the name of the job in your workflow that publish the packages(s)
-    uses: genexuslabs/build-genexus-reusable-workflow/.github/workflows/commit-to-git.yml@main
-    needs: buildJob
-    with:
-      VERSION: ${{ needs.buildJob.outputs.PACKAGE_VERSION }}
-      PACKAGE_NAMES: ${{ needs.buildJob.outputs.PACKAGES_NAME }}    # Optional
-    secrets: inherit
+    update-genexus-dependency:
+      # Replace the 'buildJob' name in the following lines for the name of the job in your workflow that publish the packages(s)
+      uses: genexuslabs/build-genexus-reusable-workflow/.github/workflows/update-genexus-dep-version.yml@main
+      needs: buildJob
+      with:
+        VERSION: ${{ needs.buildJob.outputs.PACKAGE_VERSION }}
+        PACKAGE_NAMES: ${{ needs.buildJob.outputs.PACKAGES_NAME }}    # Optional (1)
+      secrets: inherit
 # -------------------------------------
+
+# (1) PACKAGES_NAME is optional when your have only one dependency to update and its name
+# is the same than the repo; otherwise, define this value.