@@ -33,10 +33,10 @@ They perform Gradle `check` task and Maven `verify` goal, respectively.
3333The caller workflow is as simple as follows.
3434
3535#### Gradle Pull Request caller workflow:
36- https://github.com/artembilan/spring-messaging-build-tools /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/pr-build-gradle.yml#L1-L10
36+ https://github.com/artembilan/spring-github-workflows /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/pr-build-gradle.yml#L1-L10
3737
3838#### Maven Pull Request caller workflow:
39- https://github.com/artembilan/spring-messaging-build-tools /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/pr-build-maven.yml#L1-L10
39+ https://github.com/artembilan/spring-github-workflows /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/pr-build-maven.yml#L1-L10
4040
4141You can add more branches to react for pull request events.
4242
@@ -45,10 +45,10 @@ They use JFrog CLI action to be able to publish artifacts into `libs-snapshot-lo
4545The Gradle workflow can be supplied with Gradle Enterprise secrets.
4646
4747#### Gradle SNAPSHOT caller workflow:
48- https://github.com/artembilan/spring-messaging-build-tools /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/ci-snapshot-gradle.yml#L1-L18
48+ https://github.com/artembilan/spring-github-workflows /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/ci-snapshot-gradle.yml#L1-L18
4949
5050#### Maven SNAPSHOT caller workflow:
51- https://github.com/artembilan/spring-messaging-build-tools /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/ci-snapshot-maven.yml#L1-L13
51+ https://github.com/artembilan/spring-github-workflows /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/ci-snapshot-maven.yml#L1-L13
5252
5353## Release Workflow
5454
@@ -75,7 +75,7 @@ The `gh release create` command is performed on a tag for just released version.
7575And 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).
7676
7777#### Example of Release caller workflow:
78- https://github.com/artembilan/spring-messaging-build-tools /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/release.yml#L1-L25
78+ https://github.com/artembilan/spring-github-workflows /blob/decee2963c926c34f1f52bf373a3bc1dc09f1724/samples/release.yml#L1-L25
7979
8080Such a workflow must be on every branch which is supposed to be released via GitHub actions.
8181
@@ -87,7 +87,7 @@ In the end you just need to go to the `Actions` tab on your project, press `Run
8787Such a release workflow can also be scheduled (` cron ` , fo example) against branches matrix.
8888
8989#### Scheduler workflow example:
90- https://github.com/artembilan/spring-messaging-build-tools /blob/3231d7b9b4fcd05afff3db32d34aa37565535ccb/samples/schedule-releases.yml#L1-L19
90+ https://github.com/artembilan/spring-github-workflows /blob/3231d7b9b4fcd05afff3db32d34aa37565535ccb/samples/schedule-releases.yml#L1-L19
9191
9292> ** Warning**
9393> The [ spring-artifactory-release.yml] ( .github/workflows/spring-artifactory-release.yml ) already uses 3 of 4 levels of nested reusable workflows.
@@ -101,7 +101,15 @@ For example, [Spring Integration for AWS](https://github.com/spring-projects/spr
101101Other projects may check out their samples repository and setup release version to perform smoke tests against just staged artifacts.
102102
103103#### Verify staged workflow sample:
104- https://github.com/artembilan/spring-messaging-build-tools/blob/dbd138bf504abec593bdadd882cc7a450d8eb0df/samples/verify-staged-artifacts.yml#L1-L28
104+ https://github.com/artembilan/spring-github-workflows/blob/dbd138bf504abec593bdadd882cc7a450d8eb0df/samples/verify-staged-artifacts.yml#L1-L28
105+
106+ ## Backport GitHub Issue Workflow
107+
108+ 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.
109+ See its documentation for labeling convention and respective GitHub events for calling this workflow.
110+
111+ #### Backport Issue caller workflow example:
112+
105113
106114## Gradle and Artifactory
107115
0 commit comments