Skip to content

Commit 4495a6b

Browse files
authored
Update some alt text
1 parent a2b735a commit 4495a6b

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

episodes/introduction.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,14 @@ exercises: 5
66

77
::::::::::::::::::::::::::::::::::::::: objectives
88

9-
- "Become familiar with the purpose of PRs."
9+
- Become familiar with the purpose of PRs.
1010

1111
::::::::::::::::::::::::::::::::::::::::::::::::::
1212

1313
:::::::::::::::::::::::::::::::::::::::: questions
1414

15-
- "What are Pull Requests (PRs)?"
16-
- "How do PRs help with software development?"
15+
- What are Pull Requests (PRs)?
16+
- How do PRs help with software development?
1717

1818
::::::::::::::::::::::::::::::::::::::::::::::::::
1919

@@ -25,7 +25,7 @@ main project repository. Pull requests are sent through git systems, like
2525
GitLab, GitHub, and BitBucket, to notify the rest of your team that a branch
2626
or fork is ready to be reviewed."
2727

28-
![](fig/vcs-image.png){alt='Image from Undraw.co for version control visualization'}
28+
![](fig/vcs-image.png){alt='Decorative image from Undraw.co to visualize a version control pipeline'}
2929

3030
In other words, PRs are a mechanism for introducing and merging changes
3131
into a code base in a manner that enables discussion and collaboration.
@@ -34,7 +34,7 @@ In this lesson, students will learn about better practices for GitHub PRs.
3434

3535
## How Pull Requests Fit in the Development Process
3636

37-
![](fig/gh-pr-workflow.png){alt='From Freira et al.: Visualization of the GitHub development workflow with PRs'}
37+
![](fig/gh-pr-workflow.png){alt='From Freira et al.: Visualization of the GitHub development workflow with PRs. Workflow goes from Developer to Clone to Create a Branch to individual commits to Create Pull Request to Discussion/Project Community, ending with Merge or close the PR'}
3838

3939
The development workflow can have several different formats; however, a simple
4040
one is this:
@@ -60,7 +60,7 @@ integrated and stand-alone.
6060
GitHub integrates branching and merging into their version control system. Every project
6161
on GitHub can use the integrated pull requests feature.
6262

63-
![](fig/intersect-nav.png){alt='INTERSECT training repository navigation bar'}
63+
![](fig/intersect-nav.png){alt='INTERSECT training repository navigation bar, showing, from left to right: Code, Issues, Pull Requests, Actions, Projects, Security, Insights'}
6464

6565
To access a repository's PRs, simply navigate to the repository root
6666
page and click on "Pull requests" in the navigation bar. This will take you to the
@@ -82,7 +82,7 @@ Navigate to [https://github.com/spack/spack](https://github.com/spack/spack) and
8282

8383
:::::::::::::::::::::::::::::::::::::::: keypoints
8484

85-
- "Pull Requests are a way to control the introduction of new content into a shared repository."
86-
- "Pull Requests enable better collaboration for multiple developers."
85+
- Pull Requests are a way to control the introduction of new content into a shared repository.
86+
- Pull Requests enable better collaboration for multiple developers.
8787

8888
::::::::::::::::::::::::::::::::::::::::::::::::::

0 commit comments

Comments
 (0)