downloads/mac: fix grammar #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
make the plural check work properly and add the missing word "ago" for years and months. Signed-off-by: Matthias Aßhauer <mha1993@live.de>
dscho
reviewed
Oct 23, 2023
dscho
added a commit
that referenced
this pull request
Apr 1, 2024
# The 1st commit message will be skipped: # ci: update the books via a GitHub workflow # # With this commit, the SHAs corresponding to the various repositories # containing the ProGit Book and its translations are stored in a # sparse-checkout'able directory. # # This information is then used by a scheduled workflow to determine what # needs to be updated (if anything) and then performing that task. # # Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #2 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #3 will be skipped: # fixup! ci: update the books via a GitHub workflow # This is the commit message #4: # amend! ci: update the books via a GitHub workflow ci: update the books via a GitHub workflow With this commit, the SHAs corresponding to the various repositories containing the ProGit Book and its translations are stored in a sparse-checkout'able directory. This information is then used by a scheduled workflow to determine what needs to be updated (if anything) and then performing that task. When GitHub workflows push new changes, they cannot trigger other GitHub workflows (to avoid infinite loops). Therefore, this new GitHub workflow not only synchronizes the books, but also builds the site and deploys it. Note: The code to build the site and to deploy it is provided in a custom Action, to make it reusable. It will come in handy over the next commits, where other GitHub workflows are added that likewise need to synchronize changes that desire a site rebuild & deployment. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #5 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #6 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #7 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #8 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #9 will be skipped: # fixup! ci: update the books via a GitHub workflow
dscho
added a commit
that referenced
this pull request
Apr 1, 2024
# The 1st commit message will be skipped: # ci: update the books via a GitHub workflow # # With this commit, the SHAs corresponding to the various repositories # containing the ProGit Book and its translations are stored in a # sparse-checkout'able directory. # # This information is then used by a scheduled workflow to determine what # needs to be updated (if anything) and then performing that task. # # Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #2 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #3 will be skipped: # fixup! ci: update the books via a GitHub workflow # This is the commit message #4: # amend! ci: update the books via a GitHub workflow ci: update the books via a GitHub workflow With this commit, the SHAs corresponding to the various repositories containing the ProGit Book and its translations are stored in a sparse-checkout'able directory. This information is then used by a scheduled workflow to determine what needs to be updated (if anything) and then performing that task. When GitHub workflows push new changes, they cannot trigger other GitHub workflows (to avoid infinite loops). Therefore, this new GitHub workflow not only synchronizes the books, but also builds the site and deploys it. Note: The code to build the site and to deploy it is provided in a custom Action, to make it reusable. It will come in handy over the next commits, where other GitHub workflows are added that likewise need to synchronize changes that desire a site rebuild & deployment. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #5 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #6 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #7 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #8 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #9 will be skipped: # fixup! ci: update the books via a GitHub workflow
dscho
added a commit
that referenced
this pull request
Apr 1, 2024
# The 1st commit message will be skipped: # ci: update the books via a GitHub workflow # # With this commit, the SHAs corresponding to the various repositories # containing the ProGit Book and its translations are stored in a # sparse-checkout'able directory. # # This information is then used by a scheduled workflow to determine what # needs to be updated (if anything) and then performing that task. # # Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #2 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #3 will be skipped: # fixup! ci: update the books via a GitHub workflow # This is the commit message #4: # amend! ci: update the books via a GitHub workflow ci: update the books via a GitHub workflow With this commit, the SHAs corresponding to the various repositories containing the ProGit Book and its translations are stored in a sparse-checkout'able directory. This information is then used by a scheduled workflow to determine what needs to be updated (if anything) and then performing that task. When GitHub workflows push new changes, they cannot trigger other GitHub workflows (to avoid infinite loops). Therefore, this new GitHub workflow not only synchronizes the books, but also builds the site and deploys it. Note: The code to build the site and to deploy it is provided in a custom Action, to make it reusable. It will come in handy over the next commits, where other GitHub workflows are added that likewise need to synchronize changes that desire a site rebuild & deployment. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #5 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #6 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #7 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #8 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #9 will be skipped: # fixup! ci: update the books via a GitHub workflow
dscho
added a commit
that referenced
this pull request
May 10, 2024
# The 1st commit message will be skipped: # ci: update the books via a GitHub workflow # # With this commit, the SHAs corresponding to the various repositories # containing the ProGit Book and its translations are stored in a # sparse-checkout'able directory. # # This information is then used by a scheduled workflow to determine what # needs to be updated (if anything) and then performing that task. # # Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #2 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #3 will be skipped: # fixup! ci: update the books via a GitHub workflow # This is the commit message #4: # amend! ci: update the books via a GitHub workflow ci: update the books via a GitHub workflow With this commit, the SHAs corresponding to the various repositories containing the ProGit Book and its translations are stored in a sparse-checkout'able directory. This information is then used by a scheduled workflow to determine what needs to be updated (if anything) and then performing that task. When GitHub workflows push new changes, they cannot trigger other GitHub workflows (to avoid infinite loops). Therefore, this new GitHub workflow not only synchronizes the books, but also builds the site and deploys it. Note: The code to build the site and to deploy it is provided in a custom Action, to make it reusable. It will come in handy over the next commits, where other GitHub workflows are added that likewise need to synchronize changes that desire a site rebuild & deployment. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #5 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #6 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #7 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #8 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #9 will be skipped: # fixup! ci: update the books via a GitHub workflow
dscho
added a commit
that referenced
this pull request
May 26, 2024
# The 1st commit message will be skipped: # ci: update the books via a GitHub workflow # # With this commit, the SHAs corresponding to the various repositories # containing the ProGit Book and its translations are stored in a # sparse-checkout'able directory. # # This information is then used by a scheduled workflow to determine what # needs to be updated (if anything) and then performing that task. # # Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #2 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #3 will be skipped: # fixup! ci: update the books via a GitHub workflow # This is the commit message #4: # amend! ci: update the books via a GitHub workflow ci: update the books via a GitHub workflow With this commit, the SHAs corresponding to the various repositories containing the ProGit Book and its translations are stored in a sparse-checkout'able directory. This information is then used by a scheduled workflow to determine what needs to be updated (if anything) and then performing that task. When GitHub workflows push new changes, they cannot trigger other GitHub workflows (to avoid infinite loops). Therefore, this new GitHub workflow not only synchronizes the books, but also builds the site and deploys it. Note: The code to build the site and to deploy it is provided in a custom Action, to make it reusable. It will come in handy over the next commits, where other GitHub workflows are added that likewise need to synchronize changes that desire a site rebuild & deployment. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #5 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #6 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #7 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #8 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #9 will be skipped: # fixup! ci: update the books via a GitHub workflow
dscho
added a commit
that referenced
this pull request
Jun 11, 2024
# The 1st commit message will be skipped: # ci: update the books via a GitHub workflow # # With this commit, the SHAs corresponding to the various repositories # containing the ProGit Book and its translations are stored in a # sparse-checkout'able directory. # # This information is then used by a scheduled workflow to determine what # needs to be updated (if anything) and then performing that task. # # Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #2 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #3 will be skipped: # fixup! ci: update the books via a GitHub workflow # This is the commit message #4: # amend! ci: update the books via a GitHub workflow ci: update the books via a GitHub workflow With this commit, the SHAs corresponding to the various repositories containing the ProGit Book and its translations are stored in a sparse-checkout'able directory. This information is then used by a scheduled workflow to determine what needs to be updated (if anything) and then performing that task. When GitHub workflows push new changes, they cannot trigger other GitHub workflows (to avoid infinite loops). Therefore, this new GitHub workflow not only synchronizes the books, but also builds the site and deploys it. Note: The code to build the site and to deploy it is provided in a custom Action, to make it reusable. It will come in handy over the next commits, where other GitHub workflows are added that likewise need to synchronize changes that desire a site rebuild & deployment. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> # The commit message #5 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #6 will be skipped: # fixup! fixup! ci: update the books via a GitHub workflow # The commit message #7 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #8 will be skipped: # fixup! ci: update the books via a GitHub workflow # The commit message #9 will be skipped: # fixup! ci: update the books via a GitHub workflow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
make the plural check work properly and add the missing word "ago" for years and months.
Context
https://dscho.github.io/git-scm.com/downloads/mac/ has an odd grammar issue that https://git-scm.com/download/mac doesn't. It says
https://git-scm.com/download/mac correctly says