Skip to content

content: fix a few typos #900

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nikolas wants to merge 3 commits into
base: master
Choose a base branch
from
Open

content: fix a few typos #900

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7844568
content: fix a few typos
nikolas Aug 30, 2018
f1117cf
Merge branch 'master' into content-spelling
nikolas Sep 10, 2018
798e482
Merge branch 'master' into content-spelling
janl Sep 25, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/initial-pr.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ module.exports = prBody
const branchFailed = () => md`
<summary>💥 Tests on this branch are failing. Here’s how to proceed.</summary>

To solve the issue, first find out which of the dependency’s updates is causing the problem. Then fix your code to accomodate the changes in the updated dependency. [next-update](https://www.npmjs.com/package/next-update) is a really handy tool to help you with this.
To solve the issue, first find out which of the dependency’s updates is causing the problem. Then fix your code to accommodate the changes in the updated dependency. [next-update](https://www.npmjs.com/package/next-update) is a really handy tool to help you with this.

Then push your changes to this branch and merge it.
`
Expand Down Expand Up @@ -187,7 +187,7 @@ const greenkeeperConfigInfoMessage = (info) => {
if (info.action === 'updated') {
message += 'Since this repo already has a `greenkeeper.json` config file with defined groups, Greenkeeper has only checked whether they’re still valid. '
if (info.deletedPackageFiles.length > 0) {
message += 'The follwing `package.json` files could no longer be found in the repo and have been removed from your groups config: `' + info.deletedPackageFiles.join(', ') + '`. '
message += 'The following `package.json` files could no longer be found in the repo and have been removed from your groups config: `' + info.deletedPackageFiles.join(', ') + '`. '
}
if (info.deletedGroups.length > 0) {
message += 'Also, groups which no longer have any entries have been removed: `' + info.deletedGroups.join(', ') + '`. '
Expand Down
2 changes: 1 addition & 1 deletion content/nodejs-deprecate-issue.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ ${showBlogpost(announcementURL)}
<summary>More information on this issue</summary>

Greenkeeper has checked the \`engines\` key in any \`package.json\` file, the \`.nvmrc\` file, and the \`.travis.yml\` file, if present.
- In \`engines\`, any occurance of ${nodeVersion} was replaced with ${newLowestVersion}
- In \`engines\`, any occurrence of ${nodeVersion} was replaced with ${newLowestVersion}
- \`.nvmrc\` was updated to Node.js ${nodeVersion}
- \`.travis.yml\` was only changed if there was a root-level \`node_js\` key that specified Node.js ${nodeVersion}. In this case, ${nodeVersion} was replaced with ${newLowestVersion}. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

Expand Down