From da83cb486353855682727f2bfd44610c8c956822 Mon Sep 17 00:00:00 2001 From: Feefeertr <44415024+Feefeertr@users.noreply.github.com> Date: Fri, 3 May 2019 08:36:30 -0400 Subject: [PATCH 1/2] Updated the text Changed the placement of one sentence and added a few other words for clarity. --- blogposts/sourcegraph-circleci-2.0-migration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blogposts/sourcegraph-circleci-2.0-migration.md b/blogposts/sourcegraph-circleci-2.0-migration.md index 2966f2b585e..1a449bdcdec 100644 --- a/blogposts/sourcegraph-circleci-2.0-migration.md +++ b/blogposts/sourcegraph-circleci-2.0-migration.md @@ -10,9 +10,9 @@ heroImage: /sourcegraph-mark.png published: true --- -In this post, we'll explain how Sourcegraph code search can be used to report on the progress of upgrading CircleCI config files to the 2.0 format. +In this post, we'll explain how the Sourcegraph code search can be used to report on the progress of upgrading CircleCI config files to the 2.0 format. A likely scenario could be an Engineering Manager requesting all teams upgrade to CircleCI 2.0 and wanting to track progress without human intervention. -CircleCI 2.0 officially came out of beta in July 2017, introducing a versioned config file (`.circleci/config.yml`) to replace the previous `circle.yml` file. A likely scenario could be an Engineering Manager requesting all teams upgrade to CircleCI 2.0 and wanting to track progress without human intervention. +A bit of background: CircleCI 2.0 officially came out of beta in July 2017. At that time, it introduced a versioned config file (`.circleci/config.yml`) to replace the previous `circle.yml` file. Using [Sourcegraph.com](https://sourcegraph.com/) and as an example, [Segment's open source code on GitHub](https://github.com/segmentio), let's search for repositories that contain the 1.0 `circle.yml` file: From 526a015c1ad07c661b3e1b160687e8d778aec33d Mon Sep 17 00:00:00 2001 From: "Dr. Rissy's Writing & Marketing" <44415024+Feefeertr@users.noreply.github.com> Date: Tue, 7 May 2019 07:20:00 -0400 Subject: [PATCH 2/2] Reverted the sentence I reverted the sentence in question back to its original spot. --- blogposts/sourcegraph-circleci-2.0-migration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blogposts/sourcegraph-circleci-2.0-migration.md b/blogposts/sourcegraph-circleci-2.0-migration.md index 1a449bdcdec..98eb5235ae8 100644 --- a/blogposts/sourcegraph-circleci-2.0-migration.md +++ b/blogposts/sourcegraph-circleci-2.0-migration.md @@ -10,9 +10,9 @@ heroImage: /sourcegraph-mark.png published: true --- -In this post, we'll explain how the Sourcegraph code search can be used to report on the progress of upgrading CircleCI config files to the 2.0 format. A likely scenario could be an Engineering Manager requesting all teams upgrade to CircleCI 2.0 and wanting to track progress without human intervention. +In this post, we'll explain how the Sourcegraph code search can be used to report on the progress of upgrading CircleCI config files to the 2.0 format. -A bit of background: CircleCI 2.0 officially came out of beta in July 2017. At that time, it introduced a versioned config file (`.circleci/config.yml`) to replace the previous `circle.yml` file. +A bit of background: CircleCI 2.0 officially came out of beta in July 2017. At that time, it introduced a versioned config file (`.circleci/config.yml`) to replace the previous `circle.yml` file. A likely scenario could be an Engineering Manager requesting all teams upgrade to CircleCI 2.0 and wanting to track progress without human intervention. Using [Sourcegraph.com](https://sourcegraph.com/) and as an example, [Segment's open source code on GitHub](https://github.com/segmentio), let's search for repositories that contain the 1.0 `circle.yml` file: