profile
viewpoint

sourcegraph/javascript-typescript-langserver 773

JavaScript and TypeScript code intelligence through the Language Server Protocol

sorbo/tcpcrypt 215

Fast TCP encryption

codecov/sourcegraph-codecov 50

See code coverage information from Codecov on GitHub, Sourcegraph, and other tools.

sourcegraph/jsonx 19

Extended JSON parser and writer for Go

sourcegraph/jsonschemadoc 8

Generate Markdown documentation from a JSON Schema

sqs/avro-json 4

(NOTE: This has been merged into Avro trunk, in lang/js. Use that code from now on.) Avro JSON validator and Javascript record builder

sqs/acorn 1

A small, fast, JavaScript-based JavaScript parser

sqs/apache-httpd 1

Apache httpd + TLS-SRP

sqs/avro-keyvalue 1

Avro flat map encoder and decoder (for storing nested Avro data structures in flat key-value stores)

sqs/counter 1

counter

push eventsourcegraph/about

Quinn Slack

commit sha 90d4c4957ef3bc978f781a2e9dbbbc04c32cab23

recurring meetings with me

view details

push time in 11 hours

delete branch sourcegraph/about

delete branch : team-page-no-owner

delete time in 12 hours

push eventsourcegraph/about

Quinn Slack

commit sha 7691d87da2e2f9aed9b9484ce6b3a09ebd1f458d

team page has no automatically assigned reviewer (#1342) I feel weird reviewing people's own biographies on the team page, so I'm intentionally marking this file as having no owner (and therefore no automatically assigned reviewer).

view details

push time in 12 hours

PR merged sourcegraph/about

team page has no automatically assigned reviewer

I feel weird reviewing people's own biographies on the team page, so I'm intentionally marking this file as having no owner (and therefore no automatically assigned reviewer).

+4 -0

0 comment

1 changed file

sqs

pr closed time in 12 hours

push eventsourcegraph/about

aileenrose

commit sha fcd95e59865a3ced35f498fe7ee9bcb2054f6f00

Add pronoun and pronunciation (#1336)

view details

push time in 12 hours

delete branch sourcegraph/about

delete branch : aa/profile-update

delete time in 12 hours

PR opened sourcegraph/about

team page has no automatically assigned reviewer

I feel weird reviewing people's own biographies on the team page, so I'm intentionally marking this file as having no owner (and therefore no automatically assigned reviewer).

+4 -0

0 comment

1 changed file

pr created time in 12 hours

create barnchsourcegraph/about

branch : team-page-no-owner

created branch time in 12 hours

pull request commentsourcegraph/about

not-used-useless value feedback

@mrnugget Yeah, thanks for sharing this! I do think it is an important thing to be mindful of, and I hope we can feel like we're all living this value enough to put it in the handbook.

sqs

comment created time in a day

push eventsourcegraph/about

Quinn Slack

commit sha a0ac7dc06acc230f8c283eed74c37fd9439c8830

1-1s when switching managers

view details

push time in 2 days

push eventsourcegraph/about

Quinn Slack

commit sha 81b0ca2b6f0a452e16e0d6ced16f6bd616f9f82d

note about downsides of only having structured meetings

view details

push time in 3 days

push eventsourcegraph/about

Quinn Slack

commit sha 1f9d90a669929928f0eb4210b9defbe2d7e07895

update team page

view details

push time in 3 days

push eventsourcegraph/about

Quinn Slack

commit sha c166272b78db3f3de39678b0949c4a715993c6fd

clean up firefox search section

view details

push time in 3 days

push eventsourcegraph/about

Quinn Slack

commit sha 82f60b4c4eeb10cb0935b162e0660d599e84b900

Remind people of your role in internal meetings (#1326) As we grow, it's hard for everyone (especially new people) to remember what each person does. Give a quick reminder when you're speaking at company meeting, other cross-functional meetings, and any other meetings with folks who might not know. (Thanks to Gregg for this tip!)

view details

push time in 3 days

delete branch sourcegraph/about

delete branch : intro-yourself-in-meeetings

delete time in 3 days

PR merged sourcegraph/about

Remind people of your role in internal meetings

As we grow, it's hard for everyone (especially new people) to remember what each person does. Give a quick reminder when you're speaking at company meeting, other cross-functional meetings, and any other meetings with folks who might not know.

(Thanks to Gregg for this tip!)

+2 -0

0 comment

2 changed files

sqs

pr closed time in 3 days

create barnchsourcegraph/about

branch : intro-yourself-in-meeetings

created branch time in 3 days

PR opened sourcegraph/about

Remind people of your role in internal meetings

As we grow, it's hard for everyone (especially new people) to remember what each person does. Give a quick reminder when you're speaking at company meeting, other cross-functional meetings, and any other meetings with folks who might not know.

(Thanks to Gregg for this tip!)

+2 -0

0 comment

2 changed files

pr created time in 3 days

push eventsourcegraph/about

Quinn Slack

commit sha 326905678e333570fd9e8e63708877cde715a97a

add auto-compiled goals page, add top company goals (#1305) The goals page now (automatically) compiles the goals from other pages in the handbook. All existing handbook pages with goal content are included. Also adds the top company goals.

view details

push time in 3 days

delete branch sourcegraph/about

delete branch : goals-202007

delete time in 3 days

PR merged sourcegraph/about

add auto-compiled goals page, add top company goals

The goals page now (automatically) compiles the goals from other pages in the handbook. All existing handbook pages with goal content are included.

Also adds the top company goals.

image

+221 -73

0 comment

5 changed files

sqs

pr closed time in 3 days

push eventsourcegraph/about

Quinn Slack

commit sha fe8db022b867516ae9820f3dbffac9fe871cf89b

not-used-useless value feedback (#1308)

view details

push time in 4 days

delete branch sourcegraph/about

delete branch : used-useless-value-feedback

delete time in 4 days

PR merged sourcegraph/about

not-used-useless value feedback

This value is not actually lived by the team. It is aspirational. We will propose adding it back once we feel we are living it more or are ready to do so.

+0 -3

2 comments

1 changed file

sqs

pr closed time in 4 days

pull request commentsourcegraph/about

not-used-useless value feedback

This value is not actually lived by the team. It is aspirational. We will propose adding it back once we feel we are living it more or are ready to do so.

sqs

comment created time in 4 days

push eventsourcegraph/about

Quinn Slack

commit sha a72169ce34f99246cbe9400eff4c7d39584c97c2

Remove not-used-useless value This value is not actually lived by the team. It is aspirational. We will propose adding it back once we feel we are living it more or are ready to do so.

view details

push time in 4 days

push eventsourcegraph/about

Quinn Slack

commit sha 1e5be809941e92a9b8217860043731b60ccb6d96

remove long-outdated ceo role entry

view details

Tomás Senart

commit sha b029d40669125b1be188008f8c69c27b6881ce7c

cloud: Team page updates (#1295) * cloud: Team page updates This commit updates the Cloud team page with a number of changes: - Latest planning process - Daily updates - Changing weekly updates to be goal updates rather than personal ones - Retrospectives section - Team syncs - Full stack engineer in Hiring section (job req TBD and discussed with the team in the next sync) * Update handbook/engineering/cloud/index.md

view details

Loïc Guychard

commit sha 2dd6e6214114aca326287b04a4e6db8a470f21f8

Generalize onboarding process (#1289) As discussed during the product/eng manager sync, lifts up the new web onboarding process to apply to all new engineering hires.

view details

Loïc Guychard

commit sha 60cb987bef9b303fe1df0fda55bcf3f341cf2b43

Add docs for class->function component conversion (#1306)

view details

Austin Harshberger

commit sha 8e4af1ce617fed081be74c366d557b14a82a3f0f

Add Figma to CE onboarding in the Product section (#1307) In the Product Sync today, Christina suggested CEs have access to Figma so we can make suggestions on design, etc. The access is optional but thought I'd add this here to streamline any access questions in the future.

view details

AlicjaSuska

commit sha da184f55c8bd8390a42e3b14afac5a05af369548

Add items to the Product onboarding (#1281)

view details

Chayim

commit sha d1168b14d3fe7968c91348acceeeea9d2752f978

Security roles and responsibilities (#1302) * Roles and resposibilities Moving the roles and responsibilities from the job description and into the team page. I also took the opportunity to remove deplicates. Co-authored-by: Nick Snyder <nick@sourcegraph.com>

view details

aileenrose

commit sha 202966976cd5bfc29fae6b537d9db1b1d07afeff

Add local development instructions (#1304) For documentation only.

view details

Nick Snyder

commit sha 6a8c26b7d93f637426c3cdf71c94f4625e4a0c20

setup calendar first

view details

Quinn Slack

commit sha 60f158ee4868092e762456308846cc682dde8466

add auto-compiled goals page, add top company goals The goals page now (automatically) compiles the goals from other pages in the handbook. All existing handbook pages with goal content are included. Also adds the top company goals.

view details

push time in 5 days

PR opened sourcegraph/about

not-used-useless value feedback

The marketing team had good feedback about this value. I'd love to hear more feedback from marketing folks here so we can revise this value.

+2 -0

0 comment

1 changed file

pr created time in 5 days

create barnchsourcegraph/about

branch : used-useless-value-feedback

created branch time in 5 days

push eventsourcegraph/about

Quinn Slack

commit sha 81e7bb6b28aebee4415e75736b6acae7a114d78c

add auto-compiled goals page, add top company goals The goals page now (automatically) compiles the goals from other pages in the handbook. All existing handbook pages with goal content are included. Also adds the top company goals.

view details

push time in 5 days

PR opened sourcegraph/about

add auto-compiled goals page, add top company goals

The goals page now (automatically) compiles the goals from other pages in the handbook. All existing handbook pages with goal content are included.

Also adds the top company goals.

+219 -74

0 comment

5 changed files

pr created time in 5 days

create barnchsourcegraph/about

branch : goals-202007

created branch time in 5 days

push eventsourcegraph/about

Quinn Slack

commit sha 1e5be809941e92a9b8217860043731b60ccb6d96

remove long-outdated ceo role entry

view details

push time in 5 days

push eventsourcegraph/about

Quinn Slack

commit sha db368255be418b58271c041f221d99744034d2e5

update values (#1282)

view details

push time in 7 days

delete branch sourcegraph/about

delete branch : sqs/values

delete time in 7 days

PR merged sourcegraph/about

update values

Background: We want our values to be up to date, frequently useful, and frequently referred to. The current list (people, journey, and progress) was well intentioned, and those things still matter, but they were vague and not actually frequently useful or referred to. (We still value people, obviously, but our actual actions, and the more detailed principles in this PR, are what matter, not a word on a page.) In https://github.com/sourcegraph/about/pull/1051 and RFC 126, we reevaluated them and started to come up with more useful values. That effort stalled because it (like our previous values) sought to cover everything that mattered, which was very difficult.

This update to our values starts over from scratch and intends only to cover the values we actually frequently find useful and refer to. It's bootstrapped by values that @nicksnyder and I wrote that we have verbally referred to frequently in recent weeks.

Reviewing this PR means reviewing 2 things:

  1. The new definition/scope of values: (new) listing what's useful vs. (old) trying to cover everything that matters.
  2. The 3 initial values listed here that we've seeded this page with.

If you have other values you'd like to propose, make a PR on top of this branch or wait until this PR is merged to propose additions.

+25 -8

1 comment

2 changed files

sqs

pr closed time in 7 days

push eventsourcegraph/about

Quinn Slack

commit sha f709136eabd1ee3ea09ee29a0144aad7d80ef496

mention education budget

view details

push time in 7 days

pull request commentsourcegraph/about

update values

I'm going to merge this. I haven't heard anyone object to this new way of defining values, and we can always change them later.

sqs

comment created time in 7 days

push eventsourcegraph/about

Quinn Slack

commit sha 51a16db2f6edac08d9271c1bfc2616070101515e

mention education budget

view details

push time in 7 days

push eventsourcegraph/about

Quinn Slack

commit sha 7f32717748ddc0961fad0d35a1a3d639e08b4310

add informal description of Big Code (#1283)

view details

Christina Forney

commit sha 6969375756c180fd25a66bd8a23fac4f87be699f

Product team goals (#1262)

view details

Quinn Slack

commit sha 14101c005cbdb3cd3bd9d6bf89e2b6ff0b5b0154

good goal

view details

Beyang Liu

commit sha cf334741b6add4903eeb699a47e6d461eb503553

Revert "Add new onboarding process for web teammates (#1259)" This reverts commit b8f71b9579c73a7edd3def5fa2ac61e2dcd26d44.

view details

Loïc Guychard

commit sha 6cda34f24061ad138ccf4385f5532676ef938253

Revert "Revert "Add new onboarding process for web teammates (#1259)"" This reverts commit cf334741b6add4903eeb699a47e6d461eb503553.

view details

Dax McDonald

commit sha c9b04c134bb18fa83589d702e0ab2e62729f4e51

Update release issue template (#1254) * Update release issue template Updates to make the release more straightforward for future releases * Update release tracking issue to ask product Going forward the release captain should be requesting blog posts updates from the product team

view details

Stephen Gutekanst

commit sha 6741ecdb90f045575169b5e35824f88cd3355ed0

distribution: architecture, security, cost estimation, creation, operations, and more (#1284) Open-sourcing our docs for managed instances

view details

Nick Snyder

commit sha 0c3aa62c17dda7b47dd9f3d9f767530de52e2c3d

Run build on every commit to master (#1286)

view details

Nick Snyder

commit sha 32aa286d0d6e596f5e34e1f2370cd78c0ab34e0b

fix link

view details

Loïc Guychard

commit sha 9e103d22c681b3876e0bf8450c35e33687b7b02b

Update web team handbook page (#1287) - Remove duplicate link to onboarding process - Reflect that TJ has joined the team - Reflect that Simon is no longer part of the team

view details

Felix Becker

commit sha 2fdb108a23c0e894b851f1257faf738761e36c12

Add @felixfbecker to team locations map

view details

Felix Becker

commit sha 2d1947b55a2d26bb94af1d23933ecf94dafb8bb8

Remove Tommy Roberts from team locations map

view details

Chayim

commit sha 9c2b20a21460ca44d2a4ea0cfb325bc487f42a48

Update index.md

view details

Bunny

commit sha 42b50163da72f913fc07d8f6a1ba917153713144

Fixes in line with handbook (#1288) * Fixes in line with handbook * Removed hyphen

view details

Beyang Liu

commit sha db443fca29035244b0c4a3a43bbad446562f7c72

podcast: rvtond

view details

Beyang Liu

commit sha a91343a77bbca38f5a53aa1614eccab1094ded8b

podcast: update rvtond

view details

Austin Harshberger

commit sha 875ee32b23880d4b254a5d14ae37e8c77482d202

Adding Austin Harshberger to company/team/index.md (#1291) Adding new hire Austin Harshberger from Customer Engineering to company/team/index per [new hire onboarding tasks](https://about.sourcegraph.com/handbook/people-ops/onboarding#for-all-new-teammates). Please let me know if there are any typos or suggested edits, cheers!

view details

Austin Harshberger

commit sha 450ad2c42f108d3455ab555ae447511fc5366de8

Removing first sentence for Austin Harshberger due to typo (#1292) Just realized the first sentence of my bio was supposed to be third person and not first, so in everlasting embarrassment I am creating this PR to remove it so it's not eternalized in time 🤪

view details

aileenrose

commit sha 4da715da47a7196f9ffc09b863f5d2261d093bfb

Create component for Get Started (#1293) * Create component for Get Started * Lighten up gradient and update headings

view details

Nick Snyder

commit sha 110d3fd0784e18fc5e340aeb369d15bf7a3a2264

Update docsite to 1.4 (#1285)

view details

push time in 7 days

push eventsourcegraph/about

Quinn Slack

commit sha 14101c005cbdb3cd3bd9d6bf89e2b6ff0b5b0154

good goal

view details

push time in 8 days

push eventsourcegraph/about

Quinn Slack

commit sha 7f32717748ddc0961fad0d35a1a3d639e08b4310

add informal description of Big Code (#1283)

view details

push time in 8 days

delete branch sourcegraph/about

delete branch : big-code-informal

delete time in 8 days

PR opened sourcegraph/about

add informal description of Big Code
+2 -0

0 comment

1 changed file

pr created time in 8 days

create barnchsourcegraph/about

branch : big-code-informal

created branch time in 8 days

push eventsourcegraph/about

Beyang Liu

commit sha cab0335955bada9ed5f2663a6c2e8f9278f08fb9

podcast: publish dan bentley

view details

Quinn Slack

commit sha a0f5fd8c59314668b3d8a5c108ea79cab196ef86

update values Background: We want our values to be up to date, frequently useful, and frequently referred to. The current list (people, journey, and progress) was well intentioned, and those things still matter, but they were vague and not actually frequently useful or referred to. (We still value people, obviously, but our actual actions, and the more detailed principles in this PR, are what matter, not a word on a page.) In https://github.com/sourcegraph/about/pull/1051 and [RFC 126](https://docs.google.com/document/d/1_L-XOT4oPTOuUkT4_JMykneo_wPn2WqC2BXR6_-U5dI/edit#heading=h.trqab8y0kufp), we reevaluated them and started to come up with more useful values. That effort stalled because it (like our previous values) sought to cover everything that mattered, which was very difficult. This update to our values starts over from scratch and intends only to cover the values we actually frequently find useful and refer to. It's bootstrapped by values that @nicksnyder and I wrote that we have verbally referred to frequently in recent weeks. Reviewing this PR means reviewing 2 things: 1. The new definition/scope of values: (new) listing what's useful vs. (old) trying to cover everything that matters. 1. The 3 initial values listed here that we've seeded this page with. If you have other values you'd like to propose, make a PR on top of this branch or wait until this PR is merged to propose additions.

view details

push time in 8 days

push eventsourcegraph/about

Quinn Slack

commit sha 437889e57afb4fba68deeaa35e7f2bc065b806a0

update values Background: We want our values to be up to date, frequently useful, and frequently referred to. The current list (people, journey, and progress) was well intentioned, and those things still matter, but they were vague and not actually frequently useful or referred to. (We still value people, obviously, but our actual actions, and the more detailed principles in this PR, are what matter, not a word on a page.) In https://github.com/sourcegraph/about/pull/1051 and [RFC 126](https://docs.google.com/document/d/1_L-XOT4oPTOuUkT4_JMykneo_wPn2WqC2BXR6_-U5dI/edit#heading=h.trqab8y0kufp), we reevaluated them and started to come up with more useful values. That effort stalled because it (like our previous values) sought to cover everything that mattered, which was very difficult. This update to our values starts over from scratch and intends only to cover the values we actually frequently find useful and refer to. It's bootstrapped by values that @nicksnyder and I wrote that we have verbally referred to frequently in recent weeks. Reviewing this PR means reviewing 2 things: 1. The new definition/scope of values: (new) listing what's useful vs. (old) trying to cover everything that matters. 1. The 3 initial values listed here that we've seeded this page with. If you have other values you'd like to propose, make a PR on top of this branch or wait until this PR is merged to propose additions.

view details

push time in 8 days

PR opened sourcegraph/about

update values

Background: We want our values to be up to date, frequently useful, and frequently referred to. The current list (people, journey, and progress) was well intentioned, and those things still matter, but they were vague and not actually frequently useful or referred to. (We still value people, obviously, but our actual actions, and the more detailed principles in this PR, are what matter, not a word on a page.) In https://github.com/sourcegraph/about/pull/1051 and RFC 126, we reevaluated them and started to come up with more useful values. That effort stalled because it (like our previous values) sought to cover everything that mattered, which was very difficult.

This update to our values starts over from scratch and intends only to cover the values we actually frequently find useful and refer to. It's bootstrapped by values that @nicksnyder and I wrote that we have verbally referred to frequently in recent weeks.

Reviewing this PR means reviewing 2 things:

  1. The new definition/scope of values: (new) listing what's useful vs. (old) trying to cover everything that matters.
  2. The 3 initial values listed here that we've seeded this page with.

If you have other values you'd like to propose, make a PR on top of this branch or wait until this PR is merged to propose additions.

+25 -8

0 comment

2 changed files

pr created time in 9 days

create barnchsourcegraph/about

branch : sqs/values

created branch time in 9 days

issue commentsourcegraph/about

team-collaboration.md missing

from @nicksnyder

We currently have a broken link that got merged into master in the handbook (red build doesn’t prevent merging), but there isn’t a red build on master because netlify checks don’t run on merge? How does stuff get deployed once it is on master?

Akkuma

comment created time in 11 days

PR opened sourcegraph/about

add common question about kythe
+7 -0

0 comment

1 changed file

pr created time in 11 days

create barnchsourcegraph/about

branch : kythe-question

created branch time in 11 days

delete branch sourcegraph/about

delete branch : handbook-heroes

delete time in 11 days

push eventsourcegraph/about

Quinn Slack

commit sha 99274d3ea5ed26fff3193b99381a2e9b20e9a658

handbook heroes (#1268) https://sourcegraph.slack.com/archives/CQ44Y7F4G/p1595524932058500

view details

push time in 11 days

PR merged sourcegraph/about

handbook heroes

https://sourcegraph.slack.com/archives/CQ44Y7F4G/p1595524932058500

+1 -1

0 comment

1 changed file

sqs

pr closed time in 11 days

push eventsourcegraph/sourcegraph

Quinn Slack

commit sha 3152e468dbef3511abdfd1b7fdc3ebe891428844

wip

view details

push time in 11 days

push eventsourcegraph/sourcegraph

Quinn Slack

commit sha b240ced93486528943533a1c34c5c81cfe610b2f

remove useless @storybook/addon-info We don't use it, it just takes up pixels, and it's deprecated anyway (see https://github.com/storybookjs/storybook/issues/9211#issuecomment-568149450).

view details

Quinn Slack

commit sha 4d4f3bece7e5bc20d76d2bac40283745ee13ceef

wip

view details

push time in 11 days

PR opened sourcegraph/about

WIP gitpod instructions
+7 -3

0 comment

1 changed file

pr created time in 11 days

create barnchsourcegraph/about

branch : gitpod-editing

created branch time in 11 days

PR opened sourcegraph/about

handbook heroes

https://sourcegraph.slack.com/archives/CQ44Y7F4G/p1595524932058500

+1 -1

0 comment

1 changed file

pr created time in 12 days

create barnchsourcegraph/about

branch : handbook-heroes

created branch time in 12 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. You can now index multiple branches (not just the default branch) to make these kinds of searches much faster.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.

"custom search pages" is already mentioned as a top-level feature in this post, so it shouldn't be mentioned again here.

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.
We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's what's new in Sourcegraph 3.18:
LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. You can now index multiple branches (not just the default branch) to make these kinds of searches much faster.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.++-   [New C++ precise code intelligence solution](https://about.sourcegraph.com/blog/c-plus-plus-code-intel)++    We wrote a new LSIF indexer based on clangd. This means that developers using C and C++ now have access to precise code intelligence. Developers using the original C++ LSIF indexer based on DXP will see noticeable improvements with this new implementation; faster than before, and now with hovers.++-   [Getting notified about the health of Sourcegraph is even easier](https://about.sourcegraph.com/blog/sourcegraph-health-notification)++    Alerts are now delivered with detailed information, including links to potential solutions. Additionally, we now monitor container health and over/under-provisioning in all deployment modes -- so you will even get alerts if Sourcegraph needs more resources or could do with less!++-   [Custom search pages on Sourcegraph Cloud](https://about.sourcegraph.com/blog/custom-search-pages)++    This helps you search over code that is more relevant to you, and introduces you to interesting queries in the process. Additionally, communities can pick this up and have pages created specifically for them (for example, Kubernetes).
  • Additionally is long and formal. Also? (Same comment applies to other places where we say Additionally in this and other posts.)
  • In the linked blog post, it should say how members of a project community can request a page to be added.
  • The first sentence feels inconsistent with the rest. Instead of saying "This helps you", why not just say "You can now" (as we do elsewhere)? The latter feels user-focused, the former feels Sourcegraph-focused.

I would propose rewriting this paragraph to be more specific. "Code that is more relevant to you" is abstract/general, "code for popular projects" is specific:

You can now search all of the code for several popular open-source projects, such as Kubernetes and React, on project-specific search pages. We know many core team members of these projects use Sourcegraph, and this will help them spread the joy of code search to more contributors.

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. You can now index multiple branches (not just the default branch) to make these kinds of searches much faster.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.++-   [New C++ precise code intelligence solution](https://about.sourcegraph.com/blog/c-plus-plus-code-intel)++    We wrote a new LSIF indexer based on clangd. This means that developers using C and C++ now have access to precise code intelligence. Developers using the original C++ LSIF indexer based on DXP will see noticeable improvements with this new implementation; faster than before, and now with hovers.++-   [Getting notified about the health of Sourcegraph is even easier](https://about.sourcegraph.com/blog/sourcegraph-health-notification)++    Alerts are now delivered with detailed information, including links to potential solutions. Additionally, we now monitor container health and over/under-provisioning in all deployment modes -- so you will even get alerts if Sourcegraph needs more resources or could do with less!++-   [Custom search pages on Sourcegraph Cloud](https://about.sourcegraph.com/blog/custom-search-pages)++    This helps you search over code that is more relevant to you, and introduces you to interesting queries in the process. Additionally, communities can pick this up and have pages created specifically for them (for example, Kubernetes).++-   [Changelog](https://sourcegraph.com/github.com/sourcegraph/sourcegraph@master/-/blob/CHANGELOG.md)++    All the details for what changed and why, can be found here.

The comma after why feels weird to me. If it's needed for clarity, I would instead propose rearranging the sentence to not need a clarity fix. Something like See everything else that changed.?

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. In Sourcegraph 3.18, we now use an index on the default branch to speed up search operations, with the added capability to index branches other than the default branch.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Sourcegraph 3.18 includes several small features that have a big impact. Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.++-   [New C++ precise code intelligence solution](https://about.sourcegraph.com/blog/c-plus-plus-code-intel)++    We wrote a new LSIF indexer based on clangd. This means that developers using C and C++ now have access to precise code intelligence. Developers using the original C++ LSIF indexer based on DXP will see noticeable improvements with this new implementation; faster than before, and now with hovers.

I think it should be DXR, and DXP is a typo. See the slide notes at https://docs.google.com/presentation/d/1OQHfWxnBN46GPqwjM2B0m6J_TGsqOefipVdypGefeIM/edit#slide=id.g8b138c1ab4_0_17 (and DXR is something I am familiar with, DXP is not). @efritz can confirm.

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00
publishDate: 2020-07-20T10:00-07:00
LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. You can now index multiple branches (not just the default branch) to make these kinds of searches much faster.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.

different tense: "We added" in first sentence vs "we've improved/created" in second sentence

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. You can now index multiple branches (not just the default branch) to make these kinds of searches much faster.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.++-   [New C++ precise code intelligence solution](https://about.sourcegraph.com/blog/c-plus-plus-code-intel)++    We wrote a new LSIF indexer based on clangd. This means that developers using C and C++ now have access to precise code intelligence. Developers using the original C++ LSIF indexer based on DXP will see noticeable improvements with this new implementation; faster than before, and now with hovers.

The ; faster than before, and now with hovers. part of the sentence sounds weird to me. It is a sentence fragment. It would sound better if it was changed to something like : it's faster and has hovers.

LaureenH

comment created time in 13 days

PR opened sourcegraph/sourcegraph

Reviewers
use new sourcegraphstatic.com host for static assets

The https://sourcegraphstatic.com site serves content from the sourcegraph-assets Google Cloud Storage bucket. We are using this hostname instead of https://storage.googleapis.com/sourcegraph-assets/ because the latter is blocked by some ad blockers, which means our assets are not visible to many of our users.

fastmod https://storage.googleapis.com/sourcegraph-assets/ https://sourcegraphstatic.com/

Related PR: https://github.com/sourcegraph/about/pull/1252

<!-- Reminder: Have you updated the changelog and relevant docs (user docs, architecture diagram, etc) ? -->

+22 -22

0 comment

11 changed files

pr created time in 13 days

create barnchsourcegraph/sourcegraph

branch : assets-dns

created branch time in 13 days

push eventsourcegraph/about

Quinn Slack

commit sha e974c8f2a962162352e0ed1b0a1935b1ae1f4a7b

use new sourcegraphstatic.com host for static assets The https://sourcegraphstatic.com site serves content from the `sourcegraph-assets` Google Cloud Storage bucket. We are using this hostname instead of https://storage.googleapis.com/sourcegraph-assets/ because the latter is blocked by some ad blockers, which means our assets are not visible to many of our users. `fastmod https://storage.googleapis.com/sourcegraph-assets/ https://sourcegraphstatic.com/`

view details

push time in 13 days

PR opened sourcegraph/about

Reviewers
use new sourcegraphstatic.com host for static assets

The https://sourcegraphstatic.com site serves content from the sourcegraph-assets Google Cloud Storage bucket. We are using this hostname instead of https://storage.googleapis.com/sourcegraph-assets/ because the latter is blocked by some ad blockers, which means our assets are not visible to many of our users.

+86 -86

0 comment

17 changed files

pr created time in 13 days

create barnchsourcegraph/about

branch : assets-dns

created branch time in 13 days

issue openedsourcegraph/about

Blog bottom button links are broken

The 2 links at the bottom of each blog post are broken. For example, at https://about.sourcegraph.com/blog/search-multiple-revisions:

  • Read more posts goes to https://about.sourcegraph.com/blog/search-multiple-revisions/blog (404)
  • Edit this post goes to https://github.com/sourcegraph/about/edit/master/blogposts/search-across-revisions.md (404)

created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. In Sourcegraph 3.18, we now use an index on the default branch to speed up search operations, with the added capability to index branches other than the default branch.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Sourcegraph 3.18 includes several small features that have a big impact. Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.++-   [New C++ precise code intelligence solution](https://about.sourcegraph.com/blog/c-plus-plus-code-intel)++    We wrote a new LSIF indexer based on clangd. This means that developers using C and C++ now have access to precise code intelligence. Developers using the original C++ LSIF indexer based on DXP will see noticeable improvements with this new implementation; faster than before, and now with hovers.++-   [Getting notified about the health of Sourcegraph is even easier](https://about.sourcegraph.com/blog/sourcegraph-health-notification)++    Alerts are now delivered with detailed information, including links to potential solutions. Additionally, we now monitor container health and over/under provisioning in all deployment modes -- so you will even get alerts if Sourcegraph needs more resources or could do with less!

I would write "over-provisioning" and "under-provisioning", so I think it should be "over/under-provisioning" with a hyphen (instead of "over/under provisioning" with a space).

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. In Sourcegraph 3.18, we now use an index on the default branch to speed up search operations, with the added capability to index branches other than the default branch.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Sourcegraph 3.18 includes several small features that have a big impact. Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.++-   [New C++ precise code intelligence solution](https://about.sourcegraph.com/blog/c-plus-plus-code-intel)++    We wrote a new LSIF indexer based on clangd. This means that developers using C and C++ now have access to precise code intelligence. Developers using the original C++ LSIF indexer based on DXP will see noticeable improvements with this new implementation; faster than before, and now with hovers.++-   [Getting notified about the health of Sourcegraph is even easier](https://about.sourcegraph.com/blog/sourcegraph-health-notification)++    Alerts are now delivered with detailed information, including links to potential solutions. Additionally, we now monitor container health and over/under provisioning in all deployment modes -- so you will even get alerts if Sourcegraph needs more resources or could do with less!++-   [Custom search pages on Sourcegraph Cloud](https://about.sourcegraph.com/blog/custom-search-pages)++    Sourcegraph 3.18 has added new search pages that scope searches to a collection of repositories. This helps new users coming to Sourcegraph search over code that is more relevant to them, and introduces them to interesting queries in the process. Many communities will be excited to pick this up and have pages created specifically for them (for example, Kubernetes).

First sentence is mostly a restatement of the title "Custom search pages on Sourcegraph Cloud". I think we can cut the first sentence, and then restate the rest by talking to "you" instead of about "new users".

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. In Sourcegraph 3.18, we now use an index on the default branch to speed up search operations, with the added capability to index branches other than the default branch.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Sourcegraph 3.18 includes several small features that have a big impact. Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.++-   [New C++ precise code intelligence solution](https://about.sourcegraph.com/blog/c-plus-plus-code-intel)++    We wrote a new LSIF indexer based on clangd. This means that developers using C and C++ now have access to precise code intelligence. Developers using the original C++ LSIF indexer based on DXP will see noticeable improvements with this new implementation; faster than before, and now with hovers.

What is DXP?

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. In Sourcegraph 3.18, we now use an index on the default branch to speed up search operations, with the added capability to index branches other than the default branch.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Sourcegraph 3.18 includes several small features that have a big impact. Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.

The first sentence is a restatement of the "Small but mighty new features" title. I think the first sentence can be cut.

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. In Sourcegraph 3.18, we now use an index on the default branch to speed up search operations, with the added capability to index branches other than the default branch.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).

Instead of saying separated by : in your query, which I don't think people will understand ("where do I put the :?"), I would recommend just giving an example.

As for the canonical example of when this is useful, IMO it is "See all release branches that contain a particular bug so you can be sure to fix it in all the right places", not the example listed.

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. In Sourcegraph 3.18, we now use an index on the default branch to speed up search operations, with the added capability to index branches other than the default branch.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Sourcegraph 3.18 includes several small features that have a big impact. Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.++-   [New C++ precise code intelligence solution](https://about.sourcegraph.com/blog/c-plus-plus-code-intel)++    We wrote a new LSIF indexer based on clangd. This means that developers using C and C++ now have access to precise code intelligence. Developers using the original C++ LSIF indexer based on DXP will see noticeable improvements with this new implementation; faster than before, and now with hovers.++-   [Getting notified about the health of Sourcegraph is even easier](https://about.sourcegraph.com/blog/sourcegraph-health-notification)++    Alerts are now delivered with detailed information, including links to potential solutions. Additionally, we now monitor container health and over/under provisioning in all deployment modes -- so you will even get alerts if Sourcegraph needs more resources or could do with less!++-   [Custom search pages on Sourcegraph Cloud](https://about.sourcegraph.com/blog/custom-search-pages)++    Sourcegraph 3.18 has added new search pages that scope searches to a collection of repositories. This helps new users coming to Sourcegraph search over code that is more relevant to them, and introduces them to interesting queries in the process. Many communities will be excited to pick this up and have pages created specifically for them (for example, Kubernetes).

(Arguably?) different tense from above - "Sourcegraph 3.18 includes" vs. "Sourcegraph 3.18 has added".

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. In Sourcegraph 3.18, we now use an index on the default branch to speed up search operations, with the added capability to index branches other than the default branch.++-   [Search across multiple revisions](https://about.sourcegraph.com/blog/search-multiple-revisions)++    You can now search across multiple revisions of the same repository by listing multiple branch names (or other revision specifications) separated by `:` in your query. This helps you understand the differences between code at different branches (especially for release branches that have diverged).++-   [Small but mighty new features](https://about.sourcegraph.com/blog/small-and-mighty-features)++    Sourcegraph 3.18 includes several small features that have a big impact. Based on lots of feedback, we added support for campaigns in GitLab. We’ve also improved privacy feedback when adding repositories, and created custom search pages for Sourcegraph Cloud.++-   [New C++ precise code intelligence solution](https://about.sourcegraph.com/blog/c-plus-plus-code-intel)++    We wrote a new LSIF indexer based on clangd. This means that developers using C and C++ now have access to precise code intelligence. Developers using the original C++ LSIF indexer based on DXP will see noticeable improvements with this new implementation; faster than before, and now with hovers.++-   [Getting notified about the health of Sourcegraph is even easier](https://about.sourcegraph.com/blog/sourcegraph-health-notification)++    Alerts are now delivered with detailed information, including links to potential solutions. Additionally, we now monitor container health and over/under provisioning in all deployment modes -- so you will even get alerts if Sourcegraph needs more resources or could do with less!++-   [Custom search pages on Sourcegraph Cloud](https://about.sourcegraph.com/blog/custom-search-pages)++    Sourcegraph 3.18 has added new search pages that scope searches to a collection of repositories. This helps new users coming to Sourcegraph search over code that is more relevant to them, and introduces them to interesting queries in the process. Many communities will be excited to pick this up and have pages created specifically for them (for example, Kubernetes).++-   [Changelog](https://sourcegraph.com/github.com/sourcegraph/sourcegraph@master/-/blob/CHANGELOG.md)++    All the details for what changed and why, can be found here.+++## Thank you!++Thank you to the many people who contributed to Sourcegraph since the last release!++-   [@Jaxkr](https://github.com/Jaxkr)+-   [@aisbaa](https://github.com/aisbaa)+-   [@abitrolly](https://github.com/abitrolly)+-   [@smaifullerton-wk](https://github.com/smaifullerton-wk)+-   [@terinjokes](https://github.com/terinjokes)+-   [@svrx](https://github.com/svrx)+-   [@DolceTriade](https://github.com/DolceTriade)+-   [@shadyabhi](https://github.com/shadyabhi)+-   [@blanet](https://github.com/blanet)+-   [@bb-qq](https://github.com/bb-qq)+-   [@byrongrogan](https://github.com/byrongrogan)+-   [@mipearson](https://github.com/mipearson)+-   [@kwangil-ha](https://github.com/kwangil-ha)+-   [@s-yadav](https://github.com/s-yadav)+-   [@lf-](https://github.com/lf-)+-   [@smcallis](https://github.com/smcallis)+-   [@zgrimshell](https://github.com/zgrimshell)+-   [@jlangston](https://github.com/jlangston)++## Share your feedback++We want to hear what you think about Sourcegraph! If there’s something coming you are curious about or you have a specific feature you want to request,

This is an area where we could sprinkle in some social proof. "Whether you use Sourcegraph 20 times per day or are new to it, we'd love to hear what you think: (bullet list)"

LaureenH

comment created time in 13 days

Pull request review commentsourcegraph/about

3.18 release blog

+---+title: "Sourcegraph 3.18: Search across multiple revisions and non-master branches, custom search pages, campaigns now support GitLab, new C++ precise code intelligence"+author: Laureen Hudson+publishDate: 2020-MM-20T10:00-07:00+tags: [blog]+slug: sourcegraph-3.18+heroImage: /blog/3.18-release-blog-img.jpg+published: true+---++We’re improving Sourcegraph universal code search continuously, to help you solve the Big Code problems you face, all day every day. Here's how we're doing it.++-   [Indexed non-master branches](https://about.sourcegraph.com/blog/indexed-non-master-branches)++    Often, you need to search code that isn’t in your default branch, like long-lived release branches or important tags. In Sourcegraph 3.18, we now use an index on the default branch to speed up search operations, with the added capability to index branches other than the default branch.
  • We've always used an index on the default branch to speed up search. That isn't new. The new part is the "added capability" mentioned here.
  • "search operations" sounds redundant/awkward, kind of like "code search engine" vs "code search". Just saying "speed up search" is fine and more common.
  • The value here is "you can search non-default branches much faster now". The indexing is just the "how", and I don't think we convey the value clearly here. I think the 2nd sentence here needs to make the point clearly, something like "You can now index multiple branches (not just the default branch) to make these kinds of searches much faster."
LaureenH

comment created time in 13 days

create barnchsourcegraph/sourcegraph

branch : sqs/campaigns-mock

created branch time in 13 days

issue openedsourcegraph/sourcegraph

Search was fast yesterday, now times out

Will add more...

yesterday this query was fast: https://sourcegraph.com/search?q=import+yaml+and+load%28+lang:python&patternType=structural

Now it is timing out. After a while:

text search failed: failed to search github.com/bioconda/bioconda-recipes@: searcher request failed: Get "http://10.164.1.136:3181?CombyRule=&Commit=25ace29ac3cefec4dd726500f4fc0bab1ef7de26&Deadline=2020-07-21T22%3A00%3A09.769850718Z&ExcludePattern=&FetchTimeout=51.801355963s&FileMatchLimit=5000&IncludePatterns=scripts%2Fucsc%2Fcreate-ucsc-packages.py&IsStructuralPat=true&Languages=python&PathPatternsAreRegExps=true&Pattern=import+yaml&PatternMatchesContent=true&PatternMatchesPath=false&Repo=github.com%2Fbioconda%2Fbioconda-recipes&URL=": EOF

image

created time in 14 days

push eventsourcegraph/sourcegraph

Jackson R

commit sha a6a6af53122fc77dd5e50c0c39c8404686180919

docs: Add DocForge annotations and introduce Sourcegraph link monitoring (#12222)

view details

push time in 14 days

PR merged sourcegraph/sourcegraph

Reviewers
docs: Add DocForge annotations and introduce Sourcegraph link monitoring

Hello Sourcegraph team!

My name is Jackson Roberts and I’m a founder at DocForge. Keeping docs up-to-date as code changes is hard, so we've built a tool to help fast moving software teams keep everything fresh. You can see a brief description of how it works at https://docforge.dev/monitor. This pull request contains a couple sample annotations.

Additionally, we’ve built a new feature to work with the code referencing technique you already use: links to Sourcegraph searches. DocForge scans all your docs for Sourcegraph links that return no results. Then, it flags them allowing you to find these bad links and eliminate them. There are currently nine Sourcegraph searches in your documentation which return 0 results. Here’s one of them in the UI: image

We’ve spun up an instance of DocForge at https://sourcegraph.app.docforge.dev/ Thanks for being willing to try out our tool, we’re really looking forward to hearing your feedback!

+3 -0

4 comments

2 changed files

Jaxkr

pr closed time in 14 days

pull request commentsourcegraph/sourcegraph

docs: Add DocForge annotations and introduce Sourcegraph link monitoring

Nice. I just installed it. Looking forward to trying it out. It would help if you could monitor any PRs that fail the DocForge check and then write a human comment or propose a new change to help our team get used to this. :)

Jaxkr

comment created time in 14 days

pull request commentsourcegraph/sourcegraph

update docs for new campaign flow

@mrnugget:

Did you have any ideas as to what the "preview" page for a campaign spec would look like? > Now that we said we don't show a delta view there, I suppose it's a list of the CampaignSpec and its ChangesetSpecs. But when talking to @eseliger we realised that there might be different ideas here.

Erik, for example, thought along the lines of "preview page is a variation of the campaign page". I think it should be a standalone page that looks decidedly different in its layout.

I agree it should look very different in its layout, kind of like how the Amazon checkout flow cuts out a lot of the noisy nav junk. I think it should have no search bar (GlobalNavbar variant low-profile-with-logo), no breadcrumbs, just the full campaign spec and changesets with a create-campaign button.

I also think it should show all diffs and data, without the need to selectively expand/collapse.

And since we want to eventually implement a delta view, I assume, I don't think we should invest too much into the preview page. On the other hand, though, it's likely the first "campaigns" page that customers will see with the new flow.

I think many of the components will be reused between the preview page today, the campaign view page today, and the future delta view. So I don't think this is a dichotomy. The preview page today should look and feel really nice, but I don't think that will take a ton of work. Making it simple (as mentioned above) will go a long way to making it look nice. Another way in which it'll be simpler than in the past is that there will just be changesets, not patches+changesets.

sqs

comment created time in 14 days

push eventsourcegraph/about

Quinn Slack

commit sha 041d1db0e6d4d532d03d079e52f010cb1e6233e2

team can own a goal (#1239)

view details

push time in 14 days

delete branch sourcegraph/about

delete branch : own-goal

delete time in 14 days

PR merged sourcegraph/about

team can own a goal
+1 -0

0 comment

1 changed file

sqs

pr closed time in 14 days

PR opened sourcegraph/about

Reviewers
team can own a goal
+1 -0

0 comment

1 changed file

pr created time in 14 days

create barnchsourcegraph/about

branch : own-goal

created branch time in 14 days

push eventsourcegraph/about

Quinn Slack

commit sha d4e78a07086ed8b9681116a49e9b2a7d4a62f5c2

just targeting metrics is OK

view details

push time in 16 days

push eventsourcegraph/about

Dan Adler

commit sha 2cfe06d11d9a3e8ac6f9680f9e6556acde9f17a5

Refresh CE team index and add CE to org chart (#1218) * Refresh CE team index * Add CE to org chart * links * use 3rd level header * Update org_chart.md Co-authored-by: Quinn Slack <sqs@sourcegraph.com>

view details

Dan Adler

commit sha 6d682e72f821f4acf871415259ee9da89a9794cc

Update team_chat.md (#1165) Add #customer-updates to the list of channels with non-standard message retention

view details

Quinn Slack

commit sha 5e5d3e374bddf482933d647fa28dd2df3db7b24a

You can propose a hackathon if you want (#1210)

view details

Quinn Slack

commit sha 26b332cb192d7490a74c42f4e80706cedf6af394

meeting notes are not kept up to date (#1213)

view details

Quinn Slack

commit sha 4f7622a8cd708567d7d539cfd1e102bc22d9152c

Emphasize location independence of compensation (#1211)

view details

Aida DeWitt

commit sha a181a5a540b7ae8690dd353b488f99455f8faea4

Added my bio to team page (#1220)

view details

Beyang Liu

commit sha 8c2316b6a3ed7ccd9d6ff534fb3ef0421ae87e6a

podcast: more debugging

view details

Robert Lin

commit sha ddb396e0036be72f999f5b09efe541c15c3ebea0

observability: add prometheus documentation (#1201)

view details

Quinn Slack

commit sha b65df8fb575e22863ecc913ba25781d062fc5d91

edit Series B-1 blog post (#1208) * edit Series B-1 blog post * wip * copy update based on Quinn's feedback Co-authored-by: adam <41576481+adaaaam@users.noreply.github.com>

view details

adam

commit sha a1622ef360b0b74bd8d9114bd538db705fd76760

updating link to handbook

view details

Nick Snyder

commit sha 5f4e5fe6814107029c9157156c1a28d4a582e046

Clarify growth path for web team (#1217)

view details

adam

commit sha 792f87634bf7d6d3c0c50187663f3761388f8205

updating copy per Frankl's suggestions

view details

Chayim

commit sha cc94e961d3892cefcfa17645c7bbdea1ecfa0202

Linking to roadmap document

view details

Stephen Gutekanst

commit sha 1474fc20b5ffa3460a7f67d6158082fd4dfe4373

release process: ensure we always release Docker Compose and keep upgrade docs up-to-date (#1223) * patch releases: add a step to update docs * releases: add a step to update docs * release: always release Docker Compose on time * patch release: always release Docker Compose

view details

Beyang Liu

commit sha 15470b45c2434df8549708d6fa35ec8179adc9b1

Propose edits to the LSIF "year in review" blog post (#1155) Co-authored-by: Eric Fritz <eric@sourcegraph.com> Co-authored-by: Laureen Hudson <52249965+LaureenH@users.noreply.github.com>

view details

Christina Forney

commit sha c39f347832c6c0e946193d681140a431081309e6

Product docs overhaul and definition of Product documents (PD) (#1200)

view details

Loïc Guychard

commit sha c29efe8fe91704199ea8ca077f8090d339d57462

Fix T.K. start date (#1227)

view details

aileenrose

commit sha ee768d1725779ed799bfcda0269c93c7c8acef52

News updates plus fix header on uninstall page (#1222) * Fix header on uninstall. Plus add news item. * Add SVBusinessJournal

view details

aileenrose

commit sha 774a2b9b4b298dbd4e56678c961017fb3f8e2919

Add link to lightstep repo (#1224)

view details

Mimi E St Johns

commit sha fff3f302e4ebb79eef5d9fcbf7748eded9a31391

Add Mimi to team page (#1215)

view details

push time in 18 days

push eventsourcegraph/about

Quinn Slack

commit sha c322c6392cf7b533c0b3c3e2411754fcc2fc2657

Goals (not OKRs): continuous, fewer in number, less strict format (#1177) Why not just use OKRs? - Using OKRs implies a process where the goals are defined at the start of a time period and don't change until the start of the next time period. This makes people reluctant to change their goals when they are the wrong goals, which is a bad incentive. Realizing the goals are wrong and quickly changing them is way better than hitting the wrong goals. - [We don't like jargon and acronyms](https://about.sourcegraph.com/handbook/communication/style_guide#jargon-and-acronyms), and "OKR" is both. Why say "objective" when you can say "goal"? Why say "key result" and not just "result"? Questions like these make people think that there's some special science behind OKRs, when really the hard part is the fundamentally hard problem of coming up with the right goals. - There are so many ways to "do [OKRs](https://en.wikipedia.org/wiki/OKR)." Why name the overall goal-setting process after something that defines just a small part of the overall process?

view details

push time in 18 days

delete branch sourcegraph/about

delete branch : goals

delete time in 18 days

more