Skip to content

Commit a0604c8

Browse files
committed
Added summary
1 parent be074fa commit a0604c8

File tree

2 files changed

+11
-3
lines changed

2 files changed

+11
-3
lines changed

content/guided-workshop/exercises/1-code-scanning.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,10 @@ To help support developers and security teams, [GitHub Advanced Security](https:
1010

1111
Let's explore each of these, and enable them on our repository. We'll see them in action when we create a pull request with new code later in the workshop.
1212

13+
## Scenario
14+
15+
Security is important in every application. By detecting potential vulnerabilities early, teams are able to make updates before infiltrations occur. To help secure the website, the shelter wants to update the repository to ensure insecure code and libraries are detected as early as possible. You'll enable Dependabot, secret scanning, and code scanning to meet these needs.
16+
1317
## Dependabot
1418

1519
Most projects take dependencies on open source and other external libraries. While modern development would seemingly be impossible without these resources, we always need to ensure the dependencies we take are secure. [Dependabot](https://docs.github.com/en/code-security/getting-started/dependabot-quickstart-guide) will look at the dependencies your repository has and raise alerts or even create [pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to update your dependencies to a secure version.

content/guided-workshop/exercises/2-issues.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,13 @@ At their core, issues document some form of an action. They can be a request for
1212
4. Further discuss and review the pull request.
1313
5. Once everyone is satisfied and has signed off, merge the pull request and close the issue.
1414

15+
## Scenario
16+
17+
The shelter wants to begin pushing new features to the website. They want to start by displaying the hours for the current day on the landing page. There's also a need to make updates to help support development and DevOps for both current and future updates. You want to track these updates to document the work being done. You'll do this by creating issues in the repository.
18+
1519
## Creating issues to manage feature requests
1620

17-
Our project needs two main updates. We want to define a [codespace](https://github.com/features/codespaces) to enable cloud-based development for our project, and add a new component to the website to display the shelter's hours. Let's create the issues for each of these. In the next few exercises we'll begin making the appropriate updates to our project to resolve these requests.
21+
Our project needs two main updates. We want to make the updates to support development for our project, and add a new component to the website to display the shelter's hours. Let's create the issues for each of these. In the next few exercises we'll begin making the appropriate updates to our project to resolve these requests.
1822

1923
1. Return to the repository you created at the beginning of this workshop.
2024
2. Select the **Issues** tab.
@@ -24,10 +28,10 @@ Our project needs two main updates. We want to define a [codespace](https://gith
2428
| Title | Description |
2529
| ------------------------------ | ------------------------------------------------------------------------------ |
2630
| Define codespace | Create the necessary definitions for the codespace to enable cloud development |
27-
| Add component to display hours | Create a new component for the project to display the shelter's hours |
2831
| Implement testing | Create a workflow to automate testing for continuous integration |
32+
| Add component to display hours | Create a new component for the project to display the shelter's hours |
2933
| Create deployment environment | Create a workflow to create deployment environment |
30-
| Implement automated deployment | Create a workflow to automate deployment for continuous delivery |
34+
| Implement automated deployment | Create a workflow to automate deployment for continuous delivery |
3135

3236
You've now defined all the issues for the workshop! You'll use these issues to help guide your progress through the workshop.
3337

0 commit comments

Comments
 (0)