Skip to content

Commit cb84939

Browse files
committed
Update readme.md
1 parent 1b741d1 commit cb84939

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

readme.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,17 +18,17 @@ Just create your SSCCE in that file, and commit it to your fork:
1818

1919
<div align="center"><img src="https://i.imgur.com/HZP9oIg.png" /></div>
2020

21-
## Step 2 - Run your SSCCE with Travis CI / AppVeyor
21+
## Step 2 - Run your SSCCE with GitHub Actions
2222

2323
This step is **extremely easy**. Now that you have commited your SSCCE to your fork, just open a Pull Request (don't worry, *I won't accept it!*):
2424

2525
<div align="center"><img src="https://i.imgur.com/TTvuBEM.png" /></div>
2626

27-
The idea here is that once you open the pull request, GitHub Actions will automatically execute it for you, since I have them configured in the main repository. I won't accept the pull request, since the goal is just to have your code executed.
27+
The idea here is that once you open the pull request, GitHub Actions will automatically execute it for you, since I have it configured in the main repository. I won't accept the pull request, since the goal is just to have your code executed.
2828

2929
It will run your SSCCE and show show a green checkmark (or a red X) next to the commit:
3030

31-
<div align="center"><img src="https://i.imgur.com/I2wbyVJ.png" /></div>
31+
<div align="center"><img src="https://i.imgur.com/QVAKvnz.png" /></div>
3232

3333
## What if you want to make some changes to the SSCCE?
3434

0 commit comments

Comments
 (0)