sourcegraph/javascript-typescript-langserver 798
JavaScript and TypeScript code intelligence through the Language Server Protocol
sorbo/tcpcrypt 222
Fast TCP encryption
codecov/sourcegraph-codecov 51
See code coverage information from Codecov on GitHub, Sourcegraph, and other tools.
Extended JSON parser and writer for Go
Generate Markdown documentation from a JSON Schema
(NOTE: This has been merged into Avro trunk, in lang/js. Use that code from now on.) Avro JSON validator and Javascript record builder
A small, fast, JavaScript-based JavaScript parser
Apache httpd + TLS-SRP
Avro flat map encoder and decoder (for storing nested Avro data structures in flat key-value stores)
counter
push eventsourcegraph/deploy-sourcegraph-docker
commit sha 13ceaf439f362035d58c3f416c10e5858af62a27
chore(deps): update github.com/sourcegraph/sourcegraph/enterprise/dev/ci/images commit hash to c293f39
push time in 28 minutes
startedvoutilad/vmm_clock
started time in 2 hours
PR opened sourcegraph/about
@AlicjaSuska and I were chatting and thought we should add this to eng onboarding so all engineers are aware of how they can request or track design work.
I think it applies to more than just frontend engineers since we encourage all of our engineers to take active roles in surfacing design issues, and because someone may be working on the backend that's dependent on a frontend design or is requested to comment on a design and they need to know what "stage" the design is in. I think that this section is a good place to link from if we agree that we want to include this at the onboarding level.
pr created time in 2 hours
create barnchsourcegraph/about
branch : add-design-workflow-eng-onboarding
created branch time in 2 hours
push eventsourcegraph/about
commit sha e2b268c84cca30ea2efb996c5cb871df2aace4da
Add note about hiring to code insights org chart #2395 So it's clear on the org page as well (which pulls from this page). @felixfbecker I discussed with @jeanduplessis this week and we think it makes sense that as soon as we make our first full-time hire, we become a separate team (separate retro/standup etc) so I removed the sentence about the web team parenting us.
push time in 2 hours
PR merged sourcegraph/about
So it's clear on the org page as well (which pulls from this page).
@felixfbecker I discussed with @jeanduplessis this week and we think it makes sense that as soon as we make our first full-time hire, we become a separate team (separate retro/standup etc) so I removed the sentence about the web team parenting us.
pr closed time in 2 hours
startedgonum/gonum
started time in 2 hours
push eventsourcegraph/deploy-sourcegraph-docker
commit sha f92e2292ed873a5303e353132eb7808fa16878cc
chore(deps): update github.com/sourcegraph/sourcegraph/enterprise/dev/ci/images commit hash to 5e15b04
push time in 3 hours
startedrs/zerolog
started time in 3 hours
startedliyiheng/zset
started time in 3 hours
startedstashapp/stash
started time in 3 hours
pull request commentsourcegraph/about
Adding on-call Distribution info
@emchap to Gonza's point, I can see the potential for confusion here. I think as a general rule, we should link back to the main routing issues page (https://about.sourcegraph.com/handbook/ce/routing_questions) side note: we should add rotation info there as well.
Using Gonza's proposal, something like this may work:
Escalation processes vary per-team; use the [customer issue routing glossary](https://about.sourcegraph.com/handbook/ce/routing_questions) or check their Handbook documentation for more info.
Teams with a rotation:
- Distribution issues [contact](../engineering/distribution#contacting-the-support-engineer)
comment created time in 3 hours
push eventsourcegraph/about
commit sha d6c62c2ccb0aec2634fe7aa6b59933297d6e00df
distribution: update monitoring ownership area (#2399)
push time in 5 hours
delete branch sourcegraph/about
delete branch : distribution/update-monitoring-ownership
delete time in 5 hours
PR merged sourcegraph/about
Closes https://github.com/sourcegraph/about/pull/2184 by updating our wording on our monitoring ownership area instead of adding a not-well-scoped goal.
pr closed time in 5 hours
push eventsourcegraph/deploy-sourcegraph-docker
commit sha c6d09da85fcb9f33cc678b395048a4ac70d04af6
chore(deps): update github.com/sourcegraph/sourcegraph/enterprise/dev/ci/images commit hash to 1246425
push time in 6 hours
push eventsourcegraph/deploy-sourcegraph-docker
commit sha 22de9968653c03206954dc7f187c28b8b1f9c0c6
Update Sourcegraph Prometheus / Grafana Docker images
push time in 6 hours
push eventsourcegraph/deploy-sourcegraph-docker
commit sha c84205b79a03c63a90f6ef7d4937ecaf5273b3d7
Update Sourcegraph Docker images
push time in 6 hours
push eventsourcegraph/about
commit sha 6b7f6f1657d173cd6848c29bb41687fce9629fe8
Add Tech Ops to org chart; capitalization (#2404)
push time in 6 hours
pull request commentsourcegraph/about
Add Tech Ops to org chart; capitalization
<!-- codenotify report --> Notifying subscribers in CODENOTIFY files for diff ddb099fbfcc03fd64d5d3fb7efb1aa51b21c6e16...09cb8c826febc969730ab854a31a75348846791a.
Notify | File(s) |
---|---|
@sqs | company/team/org_chart.md |
comment created time in 6 hours
push eventsourcegraph/about
commit sha ddb099fbfcc03fd64d5d3fb7efb1aa51b21c6e16
Update Tech Ops index page (#2403)
push time in 7 hours
push eventsourcegraph/deploy-sourcegraph-docker
commit sha 316370b06bdb1e9a238f6a6bc089cfcd8561813c
chore(deps): update github.com/sourcegraph/sourcegraph/enterprise/dev/ci/images commit hash to 30eb219
push time in 7 hours
push eventsourcegraph/deploy-sourcegraph-docker
commit sha 6c11c5778873f93e73a92d1c2b024105400ba7e6
Update Sourcegraph Prometheus / Grafana Docker images
push time in 7 hours