Move workflows to the .github/workflows dir

spring-artifactory-release.yml → .github/workflows/spring-artifactory-release.yml

@@ -46,7 +46,7 @@ jobs:
 
   staging:
     needs: releaseVersion
-    uses: $BUILD_TOOLS_REPO/spring-stage-release.yml@main
+    uses: $BUILD_TOOLS_REPO/.github/workflows/spring-stage-release.yml@main
     with:
       releaseVersion: ${{ needs.releaseVersion.outputs.releaseVersion }}
       buildToolArgs: ${{ inputs.buildToolArgs }}
@@ -62,7 +62,7 @@ jobs:
   promote-milestone:
     needs: [releaseVersion, staging, verify-staged]
     if: ${{ (contains(needs.releaseVersion.outputs.releaseVersion, '-M') || contains(needs.releaseVersion.outputs.releaseVersion, '-RC')) }}
-    uses: $BUILD_TOOLS_REPO/spring-artifactory-promote-milestone.yml@main
+    uses: $BUILD_TOOLS_REPO/.github/workflows/spring-artifactory-promote-milestone.yml@main
     with:
       buildName: ${{ needs.staging.outputs.buildName }}
       buildNumber: ${{ needs.staging.outputs.buildNumber }}
@@ -71,7 +71,7 @@ jobs:
   promote-ga:
     needs: [releaseVersion, staging, verify-staged]
     if: ${{ !contains(needs.releaseVersion.outputs.releaseVersion, '-') }}
-    uses: $BUILD_TOOLS_REPO/spring-artifactory-promote-central.yml@main
+    uses: $BUILD_TOOLS_REPO/.github/workflows/spring-artifactory-promote-central.yml@main
     with:
       buildName: ${{ needs.staging.outputs.buildName }}
       buildNumber: ${{ needs.staging.outputs.buildNumber }}
@@ -80,7 +80,7 @@ jobs:
   finalize:
     if: ${{ !(failure() || cancelled()) }}
     needs: [releaseVersion, promote-milestone, promote-ga]
-    uses: $BUILD_TOOLS_REPO/spring-finalize-release.yml@main
+    uses: $BUILD_TOOLS_REPO/.github/workflows/spring-finalize-release.yml@main
     with:
       milestone: ${{ needs.releaseVersion.outputs.releaseVersion }}
     secrets: inherit

spring-stage-release.yml → .github/workflows/spring-stage-release.yml

@@ -47,7 +47,7 @@ jobs:
   staging-with-gradle:
     needs: maven-or-gradle
     if: ${{ needs.maven-or-gradle.outputs.isMaven == 'false' }}
-    uses: $BUILD_TOOLS_REPO/spring-artifactory-gradle-release-staging.yml@main
+    uses: $BUILD_TOOLS_REPO/.github/workflows/spring-artifactory-gradle-release-staging.yml@main
     with:
       releaseVersion: ${{ inputs.releaseVersion }}
       gradleTasks: ${{ inputs.buildToolArgs }}
@@ -57,7 +57,7 @@ jobs:
   staging-with-maven:
     needs: maven-or-gradle
     if: ${{ needs.maven-or-gradle.outputs.isMaven == 'true' }}
-    uses: $BUILD_TOOLS_REPO/spring-artifactory-maven-release-staging.yml@main
+    uses: $BUILD_TOOLS_REPO/.github/workflows/spring-artifactory-maven-release-staging.yml@main
     with:
       releaseVersion: ${{ inputs.releaseVersion }}
       mavenArgs: ${{ inputs.buildToolArgs }}

README.md

@@ -14,7 +14,7 @@ run-name: Release current version for branch ${{ github.ref_name }}
 
 jobs:
   release:
-    uses: artembilan/spring-messaging-build-tools/spring-artifactory-release.yml@main
+    uses: artembilan/spring-messaging-build-tools/.github/workflows/spring-artifactory-release.yml@main
     with:
       buildToolArgs: dist
     secrets: inherit
@@ -30,13 +30,13 @@ If no milestone scheduled, the whole workflow is cancelled.
 Then `staging` job uses the `releaseVersion` output from the previous `releaseVersion` job and dispatch the work to Gradle or Maven jobs according to the project build tool.
 The `verify-staged` requires a `verify-staged-artifacts.yml` workflow present in the project.
 For example, [Spring Integation for AWS](https://github.com/spring-projects/spring-integration-aws) use `jfrog rt download` command to verify that released `spring-integration-aws.jar` is valid.
-Other projects may checkout their samples repository and setup release version to perform smoke tests against just staged artifacts.
+Other projects may check out their samples repository and setup release version to perform smoke tests against just staged artifacts.
 
 The next job in the workflow is to promote release from staging either to `libs-milestone-local` or `libs-release-local`(and Maven Central) according to the releasing version schema.
 
-After promotion, the `finalize` job is executed, which generates release notes using [Spring Changelog Generator](https://github.com/spring-io/github-changelog-generator) exluding repository admins from `Contributors` section.
+After promotion, the `finalize` job is executed, which generates release notes using [Spring Changelog Generator](https://github.com/spring-io/github-changelog-generator) excluding repository admins from `Contributors` section.
 Then the `gh release create` command is performed on a tag for just released version.
-And in the end the milestone is closed and specific Slack channel is notifed about release.
+And in the end the milestone is closed and specific Slack channel is notified about release.
 
 Gradle projects must not manage `com.jfrog.artifactory` plugin anymore: the `jf gradlec` command sets up this plugin and respective tasks into a project using JFrog specific Gradle init script.
 In addition, the `spring-artifactory-gradle-snapshot.yml` and `spring-artifactory-gradle-release-staging.yml` add `spring-project-init.gradle` script to provide an `artifactory` plugin settings for artifacts publications.