You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/guided-workshop/exercises/1-code-scanning.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,10 @@ To help support developers and security teams, [GitHub Advanced Security](https:
10
10
11
11
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.
12
12
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
+
13
17
## Dependabot
14
18
15
19
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.
Copy file name to clipboardExpand all lines: content/guided-workshop/exercises/2-issues.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,13 @@ At their core, issues document some form of an action. They can be a request for
12
12
4. Further discuss and review the pull request.
13
13
5. Once everyone is satisfied and has signed off, merge the pull request and close the issue.
14
14
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
+
15
19
## Creating issues to manage feature requests
16
20
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.
18
22
19
23
1. Return to the repository you created at the beginning of this workshop.
20
24
2. Select the **Issues** tab.
@@ -24,10 +28,10 @@ Our project needs two main updates. We want to define a [codespace](https://gith
0 commit comments