Change artembilan org to spring-io

Author: artembilan

.github/workflows/spring-artifactory-gradle-release-staging.yml

@@ -58,7 +58,7 @@ jobs:
       - name: Checkout Common Repo
         uses: actions/checkout@v4
         with:
-          repository: artembilan/spring-github-workflows
+          repository: spring-io/spring-github-workflows
           path: build
           show-progress: false
 

.github/workflows/spring-artifactory-gradle-snapshot.yml

@@ -40,7 +40,7 @@ jobs:
       - name: Checkout Common Repo
         uses: actions/checkout@v4
         with:
-          repository: artembilan/spring-github-workflows
+          repository: spring-io/spring-github-workflows
           path: build
           show-progress: false
 

.github/workflows/spring-artifactory-promote-central.yml

@@ -38,7 +38,7 @@ jobs:
 
       - uses: actions/checkout@v4
         with:
-          repository: artembilan/spring-github-workflows
+          repository: spring-io/spring-github-workflows
           show-progress: false
 
       - uses: jfrog/setup-jfrog-cli@v3

README.md

@@ -33,10 +33,10 @@ They perform Gradle `check` task and Maven `verify` goal, respectively.
 The caller workflow is as simple as follows.
 
 #### Gradle Pull Request caller workflow:
-https://github.com/artembilan/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/pr-build-gradle.yml#L1-L10
+https://github.com/spring-io/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/pr-build-gradle.yml#L1-L10
 
 #### Maven Pull Request caller workflow:
-https://github.com/artembilan/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/pr-build-maven.yml#L1-L10
+https://github.com/spring-io/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/pr-build-maven.yml#L1-L10
 
 You can add more branches to react for pull request events.
 
@@ -45,10 +45,10 @@ They use JFrog CLI action to be able to publish artifacts into `libs-snapshot-lo
 The Gradle workflow can be supplied with Gradle Enterprise secrets.
 
 #### Gradle SNAPSHOT caller workflow:
-https://github.com/artembilan/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/ci-snapshot-gradle.yml#L1-L18
+https://github.com/spring-io/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/ci-snapshot-gradle.yml#L1-L18
 
 #### Maven SNAPSHOT caller workflow:
-https://github.com/artembilan/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/ci-snapshot-maven.yml#L1-L13
+https://github.com/spring-io/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/ci-snapshot-maven.yml#L1-L13
 
 ## Release Workflow
 
@@ -76,7 +76,7 @@ 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 notified about release (if `SPRING_RELEASE_SLACK_WEBHOOK_URL` secret is present in the repository).
 
 #### Example of Release caller workflow:
-https://github.com/artembilan/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/release.yml#L1-L25
+https://github.com/spring-io/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/release.yml#L1-L25
 
 Such a workflow must be on every branch which is supposed to be released via GitHub actions.
 
@@ -88,7 +88,7 @@ In the end you just need to go to the `Actions` tab on your project, press `Run
 Such a release workflow can also be scheduled (`cron`, fo example) against branches matrix.
 
 #### Scheduler workflow example:
-https://github.com/artembilan/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/schedule-releases.yml#L1-L19
+https://github.com/spring-io/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/schedule-releases.yml#L1-L19
 
 > **Warning**
 > The [spring-artifactory-gradle-release.yml](.github/workflows/spring-artifactory-gradle-release.yml) (and [spring-artifactory-maven-release.yml](.github/workflows/spring-artifactory-maven-release.yml)) already uses 3 of 4 levels of nested reusable workflows.
@@ -102,15 +102,15 @@ For example, [Spring Integration for AWS](https://github.com/spring-projects/spr
 Other projects may check out their samples repository and setup release version to perform smoke tests against just staged artifacts.
 
 #### Verify staged workflow sample:
-https://github.com/artembilan/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/verify-staged-artifacts.yml#L1-L28
+https://github.com/spring-io/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/verify-staged-artifacts.yml#L1-L28
 
 ## Backport GitHub Issue Workflow
 
 The [spring-backport-issue.yml](.github/workflows/spring-backport-issue.yml) uses [Spring Backport Bot](https://github.com/spring-io/backport-bot) to create a back-port issue according to the event configured in a caller workflow.
 See its documentation for labeling convention and respective GitHub events for calling this workflow.
 
 #### Backport Issue caller workflow example:
-https://github.com/artembilan/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/backport-issue.yml#L1-L16
+https://github.com/spring-io/spring-github-workflows/blob/78b29123a17655f019d800690cc906d692f836a9/samples/backport-issue.yml#L1-L16
 
 ## Dependabot Support
 
@@ -129,7 +129,7 @@ The `spring-merge-dependabot-pr` workflow does these modifications to the Depend
 - And if milestone is scheduled, the pull request is queued for auto-merging after required checks have passed.
 
 #### Dependabot merge pull request workflow example:
-https://github.com/artembilan/spring-github-workflows/blob/710bf1214450ffb9a4d3a1cfbe12755ed2d59edc/samples/merge-dependabot-pr.yml#L1-L14
+https://github.com/spring-io/spring-github-workflows/blob/710bf1214450ffb9a4d3a1cfbe12755ed2d59edc/samples/merge-dependabot-pr.yml#L1-L14
 
 ## Gradle and Artifactory
 

samples/backport-issue.yml

@@ -11,6 +11,6 @@ on:
 
 jobs:
   backport-issue:
-    uses: artembilan/spring-github-workflows/.github/workflows/spring-backport-issue.yml@main
+    uses: spring-io/spring-github-workflows/.github/workflows/spring-backport-issue.yml@main
     secrets:
       GH_ACTIONS_REPO_TOKEN: ${{ secrets.GH_ACTIONS_REPO_TOKEN }}

samples/ci-snapshot-gradle.yml

@@ -8,7 +8,7 @@ on:
 
 jobs:
   build-snapshot:
-    uses: artembilan/spring-github-workflows/.github/workflows/spring-artifactory-gradle-snapshot.yml@main
+    uses: spring-io/spring-github-workflows/.github/workflows/spring-artifactory-gradle-snapshot.yml@main
     with:
       gradleTasks: dist
     secrets:

samples/ci-snapshot-maven.yml

@@ -8,6 +8,6 @@ on:
 
 jobs:
   build_snapshot:
-    uses: artembilan/spring-github-workflows/.github/workflows/spring-artifactory-maven-snapshot.yml@main
+    uses: spring-io/spring-github-workflows/.github/workflows/spring-artifactory-maven-snapshot.yml@main
     secrets:
       JF_ARTIFACTORY_SPRING: ${{ secrets.JF_ARTIFACTORY_SPRING }}

samples/merge-dependabot-pr.yml

@@ -11,4 +11,4 @@ jobs:
   merge-dependabot-pr:
     permissions: write-all
 
-    uses: artembilan/spring-github-workflows/.github/workflows/spring-merge-dependabot-pr.yml@main
+    uses: spring-io/spring-github-workflows/.github/workflows/spring-merge-dependabot-pr.yml@main

samples/pr-build-gradle.yml

@@ -7,4 +7,4 @@ on:
 
 jobs:
   build-pull-request:
-    uses: artembilan/spring-github-workflows/.github/workflows/spring-gradle-pull-request-build.yml@main
+    uses: spring-io/spring-github-workflows/.github/workflows/spring-gradle-pull-request-build.yml@main

samples/pr-build-maven.yml

@@ -7,4 +7,4 @@ on:
 
 jobs:
   build:
-    uses: artembilan/spring-github-workflows/.github/workflows/spring-maven-pull-request-build.yml@main
+    uses: spring-io/spring-github-workflows/.github/workflows/spring-maven-pull-request-build.yml@main