Skip to content

Commit 017c0ed

Browse files
author
github-actions
committed
Update to X in STEP and README.md
1 parent b520721 commit 017c0ed

File tree

2 files changed

+18
-15
lines changed

2 files changed

+18
-15
lines changed

.github/steps/-step.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
6
1+
X

README.md

Lines changed: 17 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -14,28 +14,31 @@ _Create two deployment workflows using GitHub Actions and Microsoft Azure._
1414
</header>
1515

1616
<!--
17-
<<< Author notes: Step 6 >>>
18-
Start this step by acknowledging the previous step.
19-
Define terms and link to docs.github.com.
17+
<<< Author notes: Finish >>>
18+
Review what we learned, ask for feedback, provide next steps.
2019
-->
2120

22-
## Step 6: Production deployment
21+
## Finish
2322

24-
_Nice work! :sparkle:_
23+
<img src=https://octodex.github.com/images/octdrey-catburn.jpg alt=celebrate width=300 align=right>
2524

26-
Great work, you've done it! You should be able to see your container image in the **Packages** section of your account on the main repository page. You can get the deployment URL in the Actions log, just like the staging URL.
25+
### Congratulations, you've completed this course!
2726

28-
### The cloud environment
27+
Here's a recap of all the tasks you've accomplished in your repository:
2928

30-
Throughout the course you've spun up resources that, if left unattended, could incur billing or consume your free minutes from the cloud provider. Once you have verified your application in production, let's tear down those environments so that you can keep your minutes for more learning!
29+
- Trigger a job based on labels
30+
- Set up the Azure environment
31+
- Spin up environment based on labels
32+
- Deploy to a staging environment based on labels
33+
- Deploy to a production environment based on labels
34+
- Destroy environment based on labels
3135

32-
### :keyboard: Activity 1: Destroy any running resources so you don't incur charges
36+
### What's next?
3337

34-
1. Create and apply the `destroy environment` label to your merged `production-deployment-workflow` pull request. If you have already closed the tab with your pull request, you can open it again by clicking **Pull requests** and then clicking the **Closed** filter to view merged pull requests.
35-
36-
Now that you've applied the proper label, let's wait for the GitHub Actions workflow to complete. When it's finished, you can confirm that your environment has been destroyed by visiting your app's URL, or by logging into the Azure portal to see it is not running.
37-
38-
2. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
38+
- [We'd love to hear what you thought of this course](https://github.com/skills/.github/discussions).
39+
- [Take another GitHub Skills Course](https://github.com/skills).
40+
- [Read the GitHub Getting Started docs](https://docs.github.com/en/get-started).
41+
- To find projects to contribute to, check out [GitHub Explore](https://github.com/explore).
3942

4043
<footer>
4144

0 commit comments

Comments
 (0)