1
- name : ~Sandbox
1
+ name : " ~Sandbox"
2
2
3
3
on :
4
4
workflow_dispatch :
5
5
6
6
jobs :
7
+ sandbox :
8
+ runs-on : ubuntu-22.04
9
+ steps :
10
+ - name : Login to GitHub Container Registry
11
+ uses : docker/login-action@v2
12
+ with :
13
+ registry : ghcr.io
14
+ username : ${{ github.repository_owner }}
15
+ password : ${{ secrets.GITHUB_TOKEN }}
7
16
8
- test-maxtext :
9
- uses : ./.github/workflows/_test_maxtext.yaml
10
- secrets : inherit
17
+ - name : Print usage
18
+ run : |
19
+ cat << EOF
20
+ This is an empty workflow file located in the main branch of your
21
+ repository. It serves as a testing ground for new GitHub Actions on
22
+ development branches before merging them to the main branch. By
23
+ defining and overloading this workflow on your development branch,
24
+ you can test new actions without affecting your main branch, ensuring
25
+ a smooth integration process once the changes are ready to be merged.
26
+
27
+ Usage:
28
+
29
+ 1. In your development branch, modify the sandbox.yml workflow file
30
+ to include the new actions you want to test. Make sure to commit
31
+ the changes to the development branch.
32
+ 2. Navigate to the 'Actions' tab in your repository, select the
33
+ '~Sandbox' workflow, and choose your development branch from the
34
+ branch dropdown menu. Click on 'Run workflow' to trigger the
35
+ workflow on your development branch.
36
+ 3. Once you have tested and verified the new actions in the Sandbox
37
+ workflow, you can incorporate them into your main workflow(s) and
38
+ merge the development branch into the main branch. Remember to
39
+ revert the changes to the sandbox.yml file in the main branch to
40
+ keep it empty for future testing.
41
+ EOF
0 commit comments