Collection of Dockerfile's and resources
Resources for teaching AWS
Instragram like feed but of cats or kittens who either are coding, or think they're coding. Used for learning AWS. More details coming soon.
ryan-blunden/docker-weekly-api 1
Turning the Docker Weekly emails into structured JSON data and a hosted API service.
ryan-blunden/es7-module-loading-starter-kit 1
Aiming to be the world's simplest setup for transpiling, linting and loading ES7.
ryan-blunden/general-assembly-swift-course-2015 1
GA iOS Mobile Course, Melbourne 2015
ryan-blunden/slack-export-viewer 1
View the export of a Slack workspace.
A list of good docker resources
push eventryan-blunden/yodaspeak-backend
commit sha bf84040cd831f2c98673a474457e035e30c22270
Force redeploy
push time in 14 hours
push eventryan-blunden/yodaspeak-frontend
commit sha 02ced7d314361980a45d0747382192fdcb5b19ec
Initial commit to repository, this is
push time in 15 hours
push eventryan-blunden/yodaspeak-frontend
commit sha d11be8b8ac70084ed06ee67840c04a76ddf104f0
Initial commit to repository, this is
push time in 17 hours
push eventryan-blunden/yodaspeak-backend
commit sha b5fdee388255ae5ad3dd64d729b33b0bfd341d7f
Initial commit to repository, this is
push time in 17 hours
push eventryan-blunden/yodaspeak-backend
commit sha df4c150c4a9879be0648e1efc36380db6de66380
Initial commit to repository, this is
push time in 17 hours
push eventryan-blunden/yodaspeak-backend
commit sha ae9d9022ff79639aa2a940ad54e73df4fb767fd4
Initial commit to repository, this is
push time in 17 hours
push eventryan-blunden/yodaspeak-backend
commit sha c0bd189e63cd40eda3e00f46d3cd9582fbce00d7
Initial commit to repository, this is
push time in 18 hours
push eventryan-blunden/yodaspeak-frontend
commit sha 15cb48586d0fdeed3efe36a6c71cae05834ad783
Initial commit to repository, this is
push time in 18 hours
push eventryan-blunden/you-speak-yoda
commit sha de97f5a244b97e717e28e4345dff8456cae364c0
Initial commit
push time in 20 hours
push eventryan-blunden/you-speak-yoda
commit sha efc3c96cebf80dfc079094d90a82e75d67ff5380
Initial commit
push time in 21 hours
push eventryan-blunden/you-speak-yoda
commit sha 347d42dde169f419baa307dd132f5fe7f28f0ada
Initial commit
push time in a day
push eventryan-blunden/you-speak-yoda
commit sha 1adba3aa7434437fc8e2a29c09803825dde54d38
Initial commit
push time in 4 days
push eventryan-blunden/you-speak-yoda
commit sha dab77d5d1f82318a59272b9fade5f5ed75c06b41
Initial commit
push time in 4 days
push eventryan-blunden/you-speak-yoda
commit sha fe88903ecf1897751b0ebc839bf176b74d74575a
Initial commit
push time in 4 days
push eventryan-blunden/you-speak-yoda
commit sha ec53afe217626ce08b5781c507e443f647e1e5ba
Initial commit
push time in 4 days
created repositoryryan-blunden/yodaspeak
For when you've thought to yourself...how would Yoda say this
created time in 4 days
startedjeffhung/python.make
started time in 8 days
startedtiangolo/fastapi
started time in 22 days
startedtiangolo/uwsgi-nginx-flask-docker
started time in 22 days
push eventryan-blunden/about
commit sha b789c3286d292eed2af6537f877b8eb225bf986e
Update Sourcegraph version to 3.17.3
push time in 24 days
fork ryan-blunden/about
Sourcegraph blog, feature announcements, and website (about.sourcegraph.com)
fork in 24 days
startedJaidedAI/EasyOCR
started time in a month
startedDopplerHQ/cli
started time in a month
startedSolido/awesome-flutter
started time in 2 months
push eventryan-blunden/learn-aws
commit sha a1620ceadba1926953099e152d70a19f9627031d
Updates
push time in 2 months
startedflutter/samples
started time in 2 months
startedTralahM/django-firebase-orm
started time in 2 months
startedfirebase/firebase-ios-sdk
started time in 2 months
push eventsourcegraph/about
commit sha c38adc7342849bdb76131783a78b53ff364e80cb
Remove Ryan from team content (#979)
push time in 2 months
delete branch sourcegraph/about
delete branch : rb-remove-ryan-from-team-content
delete time in 2 months
create barnchsourcegraph/about
branch : rb-remove-ryan-from-team-content
created branch time in 2 months
push eventsourcegraph/sourcegraph
commit sha a5ec6cf53c78cb9dd2c116d8a9618fa02b8aba85
Cache bust docs.js
push time in 2 months
push eventsourcegraph/sourcegraph
commit sha b57656ff60cb7f0d1eb76d67a72a99b47ef8e0c4
Cache bust docs.js
push time in 2 months
push eventsourcegraph/sourcegraph
commit sha 9a1a2eada4e18737b6387c453c1d69f568591e6a
Content improvements
push time in 2 months
push eventsourcegraph/sourcegraph
commit sha c71cdef447ead3dd35ab696b831960e6568a5ab9
Content improvements
push time in 2 months
issue commentsourcegraph/sourcegraph
@sqs Any ideas?
I was hoping to be able to run docsite in a Pod the same way we do locally where the path to the assets and templates is local file path. That way, the assets and templates could be in a shared volume that docsite reads from and a separate container in the Pod is responsible for automatically pulling in changes from master.
comment created time in 2 months
push eventsourcegraph/sourcegraph
commit sha 3fe2548984dc36dab7640270cc7952cbf667a50f
docs: version fix (#9776)
commit sha 1c019d500cdbd5a8e5c524546eb93ec30a925b9a
observability: add support for alerting on values that are LessOrEqual (#9780)
commit sha de1b5d756b244b85994e063ca7647fa37513b2ae
observability: convert Git Server dashboard into generated form (#9781) Before (Sourcegraph.com):  After (local dev):  Fixes #9352 Fixes #9354 Fixes #9351 Fixes #7628
commit sha fc0dfa5e9bc6dc83bab8e012f492804c87721202
Update dependency @sourcegraph/eslint-config to ^0.16.0
commit sha 4a46f4895c9c82a3176c2fb242633e29c8a588f5
observability: remove deprecated and useless / bad dashboards (#9795) * remove the deprecated "Sourcegraph Internal" > "Gitserver" dashboard Before:  - `P.90 by command`: A by-command breakdown is not generally useful because gitserver command latency is mostly determined by other commands running on the system at the same time (so "latency per command" is not useful except for debugging Git's performance itself). #9788 exists to track monitoring latency of all commands. - `QPS by command` could be useful for debugging regressions or flaws that lead us to execute too many of the same command, but Jaeger is probably better suited for this and the query could be ran manually anyway. "Running git commands" already exists in new monitoring. - `Disk space remaining`: covered by new monitoring already, but only in percentages. Filed https://github.com/sourcegraph/sourcegraph/issues/9787 - `Total running commands`: covered already in new monitoring. * remove the deprecated "Sourcegraph Internal" > "Gitserver Rev 2" dashboard Before:  - `Deadline Exceeded Rate` MAY be a useful metric, but right now is far too high and random to give any useful information. Will revisit later: https://github.com/sourcegraph/sourcegraph/issues/9786 - `Clone Queue Size`: covered by new monitoring already. - `Available Disk Space`: covered by new monitoring already, but only in percentages. Filed https://github.com/sourcegraph/sourcegraph/issues/9787 - `Echo Duration Seconds`: covered by new monitoring already. - `Latencies for commands (seconds)`: this panel is currently misleading and broken because it operating on the rate of a bucket metric (???); filed https://github.com/sourcegraph/sourcegraph/issues/9788 - `Commands Running Concurrently`: covered by new monitoring already. - `Num repos waiting on git ls-remote`: This is a heavily misleading title (makes it sound like this blocks repo actions, which it does not); covered by new monitoring already. - `Repos Cloned Rate`: Covered more effectively by clone queue size in new monitoring. - `Repos Recloned Rate`: Not yet covered, filed https://github.com/sourcegraph/sourcegraph/issues/9789 - `Repos Removed Rate`: Not yet covered, filed https://github.com/sourcegraph/sourcegraph/issues/9790 * remove the deprecated "Sourcegraph Internal" > "Overview" dashboard Before:  - `QPS by Status Code`: too high level to be useful in any way, also very misleading because it doesn't account for the fact that 90% of our requests are GraphQL where an error is a 200. - `P.90 request duration`: Too much cardinality to be useful - `Memory usage [RSS]`: Arguably the most useful on this dashboard, but still too high cardinality to be useful; superseded by https://github.com/sourcegraph/sourcegraph/issues/9791 - `Container CPU [all cores]`: broken; superseded by https://github.com/sourcegraph/sourcegraph/issues/9791 * remove useless "Sourcegraph Internal" > "Zoekt Indexserver" dashboard Honestly, there is no way this dashboard could ever be useful to anyone. How would you interpret these numbers?  New monitoring already has in place alerting for revision resolution, and https://github.com/sourcegraph/sourcegraph/issues/9783 exists to track indexing failures (not covered by this dashboard). I am not convinced "Latencies for indexing a repo (seconds)" is a useful metric, currently, either. * remove deprecated "Sourcegraph internal" > "Searcher" dashboard Before:  - `Searches by status ...`: covered by "Unindexed search request errors" in new monitoring. - `Total running requests`: not needed/useful - `Total requests served`: not needed/useful - `Errors [rate-10m]`: covered by "Unindexed search request errors" in new monitoring. - `Requests [rate-10m]`: not needed/useful - `Archive Cache ...`: Filed https://github.com/sourcegraph/sourcegraph/issues/9796 * remove obsolete "Sourcegraph Internal" > "HTTP" dashboard Before:  - `QPS by Status Code`: Not useful, most of our requests even GraphQL are 200-with-error. - `QPS by Route`: Not useful, as shown by screenshot. - `P.90 request duration`: Will be superseded by https://github.com/sourcegraph/sourcegraph/issues/9797 & currently not useful due to verbosity. - `P.90 Overall Route Duration`: Confusing with above; Will be superseded by https://github.com/sourcegraph/sourcegraph/issues/9797 & currently not useful due to verbosity.
commit sha c056b1a0be686c2cdfecc097efbfe900247c686a
Prevent spaces being added to copy-asted path (#9800)
commit sha 6fdd0e3ef693597ca167140cf5d20b1e223793f7
docker-images: fix building and publish new versions of grafana,prometheus (#9801)
commit sha 1e62f09f92f83a208532015ebda755478c5732a1
tracking-issue: Fix #9774 (#9803)
commit sha cfb7d985c81d40d7cbc046033c253b337845b2ad
dev/go-install.sh: only delete tmpdir if it exists (#9802) * dev/go-install.sh: only delete tmpdir if it exists I've run into this multiple times: $ ./enterprise/dev/start.sh [...] 12:50:41 watch | rm: /var/folders/86/23tk7bxn04vgj7slgj_qdj6m0000gn/T/src-binaries.XXXXXXXX.bcuIH78v/*: No such file or directory 12:50:41 watch | Terminating watch I don't know which condition can trigger it, but it doesn't seem wrong to be safe here. * Update dev/go-install.sh Co-Authored-By: Felix Becker <felix.b@outlook.com> Co-authored-by: Felix Becker <felix.b@outlook.com>
commit sha 9184e0b717fe34ccb6f0dc679055e0824728bc9d
tracking-issue: Fix top level PRs (#9805) * tracking-issue: Fix top level PRs * tracking-issue: Apply Joe's post-merge suggestion
commit sha 7090aff0e18ef118857b7fb68ac011e137f4b480
Update go.mod/go.sum with generated changes after booting up env (#9799) These changes showed up in my `git status` after I booted up our dev environment with `./enterprise/dev/start.sh`.
commit sha 9caafbe5f164a2311b81e8403fe8f27654e60a41
Make campaign.description nullable (#9702)
commit sha 389d67795539828cb6382ab22de35d6cb79a2b12
authz: use smaller interface to mock GitHub client in tests (#9808) * Use smaller interface to mock client * Run gofmt
commit sha b30bee8690160a4c981b0a12087f874f7db2cdf1
use sentence case in doc sidebar (#9809) ["Use 'sentence case'", from the style guide.](https://about.sourcegraph.com/handbook/communication/style_guide#general)
commit sha 8ae88ee2cc10b57e10ed0ab6ea16593992a99b0f
search: add field scanner (#9775)
commit sha 40946d9751b002ca7cac9aad0faf87dc2a5574af
search: add value scanner (#9777)
commit sha 527ecede447a76959d1b7941df52089fcc21e416
refactor Sourcegraph.com billing/license React components into… (#9764) * make ProductSubscriptionForm a React.FunctionComponent, add tests * make NewProductSubscriptionPaymentSection a React.FunctionComponent, add tests * make ProductSubscriptionUserCountFormControl a React.FunctionComponent, add tests * make ProductPlanFormControl a React.FunctionComponent, add tests * make UserSubscriptionsProductSubscriptionPage a React.FunctionComponent, add tests * simplify Product{Subscription,License}Node and related list components - make then React.FunctionComponents - remove unused props * make UserSubscriptionsNewProductSubscriptionPage a React.FunctionComponent * make UserSubscriptionsEditProductSubscriptionPage a React.FunctionComponent, add tests * make UserProductSubscriptionStatus a React.FunctionComponent, add tests * make SiteAdminProductSubscriptionPage a React.FunctionComponent * make SiteAdminGenerateProductLicenseForSubscriptionForm a React.FunctionComponent, add tests * make StripeWrapper a React.FunctionComponent * make SiteAdminCustomerBillingLink a React.FunctionComponent, add tests * make SiteAdminCustomersPage a React.FunctionComponent * make SiteAdminProductLicenseNode and SiteAdminProductSubscriptionPage React.FunctionComponents, add tests * make SiteAdminProductSubscriptionBillingLink a React.FunctionComponent, add tests
commit sha e3b1adbeecae2ac4882dea8e41fd63926fee1221
search: robust keyword scanning (#9811)
commit sha cfe49c7d97b9ad77a1456a76c6ed2a497b269992
discussions: deprecate GraphQL and config fields (#9685) This makes it easy to cleanly remove discussions code once we start working on 3.16.
commit sha c5ec090a67295b274d8d1f4bd9de7ae50d83894c
observability: use more color-blind friendly threshold colors (#9821) In this I can't tell if the color is green or orange (I have a spectacularly bad version of deuteranopia):  With the new orange color, I can identify it easily:  With the new red and orange colors both present, also much easier for me due to the higher contrast: 
push time in 2 months
pull request commentsourcegraph/sourcegraph
authz: add docs and links to background permissions syncing
If I understand this correctly, a "complete sync" is only done once at the start, either when a repository or user is first added? Then an incremental sync is just reflecting any changes in permissions that have happened since then to bring Sourcegraph up-to-date with the code host?
If that' the case, I would try adjusting the content here to explain the sequence of when each type of sync happens, and in the case of an incremental sync, what would trigger an incremental sync?
comment created time in 2 months
startedsdras/awesome-actions
started time in 3 months
startedmanojVivek/responsively-app
started time in 3 months
issue commentsourcegraph/sourcegraph
Because docsite loads the templates and assets into a virtual file system, replacing the Pod via a metadata change in the deployment YAML is the only way I can't think of right now to achieve this.
Maybe we can add something to dot-com deploy to do this automatically.
I think the solution is going to be along those lines.
comment created time in 3 months
Pull request review commentsourcegraph/about
"Livestream": [ { "eventTitle": "Livestream: Introduction to Sourcegraph Universal Code Search",- "eventDate": "Thursday, May 14, 2020 | 10:00 AM PDT",- "eventLink": "https://info.sourcegraph.com/training-universal-code-search-may14",+ "eventDate": "Thursday,June 18, 2020 | 10:00 AM PDT",
"eventDate": "Thursday, June 18, 2020 | 10:00 AM PDT",
comment created time in 3 months
issue commentsourcegraph/sourcegraph
Sourcegraph Docker container crashes on startup
here is a fresh build of 3.16 built with Go 1.14.3
@slimsag I just tested this on the AWS 20.04 community image and it worked
comment created time in 3 months
push eventsourcegraph/about
commit sha a1fad66ec4b7e1a32648c109fb7d5c612b887ad1
handbook: screen recording page fixes (#959)
push time in 3 months
push eventsourcegraph/about
commit sha fb5f7fa5c837a887dc75e855c453b591787857f4
Improve YouTube embed code that only shows Sourcegraph videos on end screen (#969)
push time in 3 months
PR opened holms/docker-rvm-alpine
This Dockerfile was vulnerable to CVE-2019-5021 as it inherits from Alpine version 3.5 and installs the shadow package.
Upgrading to alpine:3.8 mitigates this vulnerability.
pr created time in 3 months
push eventryan-blunden/docker-rvm-alpine
commit sha 9ecf33d7087d73d3b528916c678ba17a7aef6388
Upgrade to alpine:3.8 to fix CVE-2019-5021 This Dockerfile was vulnerable to [CVE-2019-5021](https://alpinelinux.org/posts/Docker-image-vulnerability-CVE-2019-5021.html) as it inherits from Alpine version 3.5 and installs the `shadow` package. Upgrading to `alpine:3.8` mitigates this vulnerability.
push time in 3 months
push eventryan-blunden/docker-rvm-alpine
commit sha b564cd0b04278869776bcb902d5d2393f20c94cb
Upgrade to alpine:3.8 to fix CVE-2019-5021 This Dockerfile was vulnerable to [CVE-2019-5021](https://alpinelinux.org/posts/Docker-image-vulnerability-CVE-2019-5021.html) as it inherits from Alpine version 3.5 and installs the `shadow` package. Upgrading to `alpine:3.8` mitigates this vulnerability.
push time in 3 months
fork ryan-blunden/docker-rvm-alpine
Dockerfile for installing RVM and latest ruby on Alpine Linux and retains build tools
fork in 3 months
push eventsourcegraph/about
commit sha 5440c5b5cf1ba2fd834fb489d87f4b70c41017d6
Updated import statements
push time in 3 months
push eventsourcegraph/about
commit sha 7dc921c4eb3209ae74944718809a4668daa1f8a8
Update YouTube code embed samples
push time in 3 months
push eventsourcegraph/about
commit sha de71c40f0e38d8e6a3704d95984db2a2c01a2edd
Update dependency ts-loader to ^7.0.4 (#911) Co-authored-by: Renovate Bot <bot@renovateapp.com>
push time in 3 months
PR merged sourcegraph/about
This PR contains the following updates:
| Package | Type | Update | New value | References | Sourcegraph |
|---|---|---|---|---|---|
| ts-loader | dependencies | patch | ^7.0.4 | source |
Release Notes
<details> <summary>TypeStrong/ts-loader</summary>
v7.0.4
v7.0.3
</details>
Renovate configuration
:date: Schedule: "on the 1st through 7th day of the month" in timezone America/Los_Angeles.
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
This PR has been generated by WhiteSource Renovate. View repository job log here.
pr closed time in 3 months
push eventsourcegraph/about
commit sha 9e0abf91ee51f615a491812f6342353dc816b1e7
Updated handbook sample
commit sha 0d267b0b12178417b4f85664f2cccdac1e3a1ddf
Update YouTube code embed samples
push time in 3 months
issue commentsourcegraph/sourcegraph
@joemccall86 @mredding10 Groovy code intelligence is now supported.
comment created time in 3 months
issue closedsourcegraph/sourcegraph
Support Groovy on Sourcegraph
closed time in 3 months
joemccall86
PR closed v2gay/docker-ocserv-radius
This Dockerfile is vulnerable to CVE-2019-5021 as it inherits from Alpine version 3.4 and installs the linux-pam package.
Upgrading to alpine:3.8 mitigates this vulnerability.
pr closed time in 3 months
PR opened boynux/freeradius-image
This Dockerfile is vulnerable to CVE-2019-5021 as it inherits from Alpine version 3.4 and installs the linux-pam package.
Upgrading to alpine:3.8 mitigates this vulnerability.
pr created time in 3 months
push eventryan-blunden/freeradius-image
commit sha e21a85c11e1f54fdd9aaadcfce9f46d6866746df
Upgrade to alpine:3.8 to fix CVE-2019-5021 This Dockerfile is vulnerable to [CVE-2019-5021](https://alpinelinux.org/posts/Docker-image-vulnerability-CVE-2019-5021.html) as it inherits from Alpine version 3.4 and installs the `linux-pam` package. Upgrading to `alpine:3.8` mitigates this vulnerability.
push time in 3 months
PR opened v2gay/docker-ocserv-radius
This Dockerfile is vulnerable to CVE-2019-5021 as it inherits from Alpine version 3.4 and installs the linux-pam package.
Upgrading to alpine:3.8 mitigates this vulnerability.
pr created time in 3 months
push eventryan-blunden/docker-ocserv-radius
commit sha e238e0a03c7f305052e0b5ff6612d3016b5ff046
Upgrade to alpine 3:8 to fix CVE-2019-5021 This Dockerfile is vulnerable to [CVE-2019-5021](https://alpinelinux.org/posts/Docker-image-vulnerability-CVE-2019-5021.html) as it inherits from Alpine version 3.4 and installs the `linux-pam` package. Upgrading to `alpine:3.8` mitigates this vulnerability.
push time in 3 months
pull request commentsourcegraph/about
Credit 3.16 external contributors
@christinaforney That script only brings in users that have created issues, not submitted pull requests. Created https://github.com/sourcegraph/about/issues/967 and I can fix by next release.
comment created time in 3 months
issue openedsourcegraph/about
Revise generate contributors script
The generate_contributors.go script needs to be revised to:
- Pull in users who have submitted a pull request
- Automatically exclude members of the Sourcegraph team without having to maintain a manual exclude list
created time in 3 months
Pull request review commentsourcegraph/about
Sourcegraph 3.16 release blog post
+---+title: "Sourcegraph 3.16: Version contexts, campaigns, and major syntax highlighting improvements"+author: Christina Forney+publishDate: 2020-05-20T10:00-07:00+tags: [+ blog+]+slug: sourcegraph-3.16+heroImage: https://about.sourcegraph.com/sourcegraph-mark.png+published: true+---++Explore, navigate, and better understand all code, everywhere, faster with Sourcegraph Universal Code Search. Uber, Lyft, Yelp, and other enterprises rely on Sourcegraph to improve developer productivity and manage large-scale code changes.++<div style="padding-left: 2rem">++[**📌 Introducing version contexts to search past releases**](#introducing-version-contexts-to-search-past-releases)<br />++[**📣 Campaigns**](#campaigns)<br />++[**🎨 Best in class syntax highlighting**](#best-in-class-syntax-highlighting)<br />++[**👀 Easier to read queries in plain text mode**](#easier-to-read-queries-in-plain-text-mode)<br />++[**🧠 Performance improvements for precise code intelligence**](#performance-improvements-for-precise-code-intelligence)<br />++[**🕵️♀️ Discover useful scopes with `repogroup` autocompletion**](#discover-useful-scopes-with-code-classlanguage-textrepogroupcode-autocompletion)<br />++[**🔑 Check syncing status of repository and user permissions**](#check-syncing-status-of-repository-and-user-permissions)<br />++[**📊 Understanding user activity of your instance**](#understanding-user-activity-of-your-instance)<br />++[**ⓘ Improvements to basic code intelligence for several languages**](#improvements-to-basic-code-intelligence-for-several-languages)<br />++[**📝 Changelog**](#changelog)<br />+Every detail that changed in this release++[**🎖️ Thank you**](#thank-you)<br />+Sourcegraph couldn't be what it is without the community.++</div>++**Deploy or upgrade:** [Local](https://docs.sourcegraph.com/#quickstart-guide) | [AWS](https://github.com/sourcegraph/deploy-sourcegraph-aws) | [DigitalOcean](https://marketplace.digitalocean.com/apps/sourcegraph?action=deploy&refcode=48dfb3ccb51c) | [Kubernetes cluster](https://github.com/sourcegraph/deploy-sourcegraph)++<div class="alert alert-info">+ <p>+ <strong>LEARN MORE:</strong><br />+ <a href="https://info.sourcegraph.com/online-meetup-may21?utm_source=blog">+ Online meetup: Sourcegraph 3.16 - Thursday, May 21 at 10AM PDT+ </a>+ </p>+</div>++## Introducing version contexts to search past releases++TODO: video++<!--+<p class="container">+ <div style="padding:56.25% 0 0 0;position:relative;">+ <iframe src="https://www.youtube.com/embed/{VIDEO_ID}" style="position:absolute;top:0;left:0;width:100%;height:100%;" frameborder="0" webkitallowfullscreen="" mozallowfullscreen="" allowfullscreen=""></iframe>+ </div>+ <p style="text-align: center"><a href="https://youtu.be/{VIDEO_ID}" target="_blank">View on YouTube</a></p>+</p>+-->++Many large organizations have old versions of code running in production and need to search across all the code for that release. Sourcegraph 3.16 introduces the ability to create a context consisting of many repositories with specific revisions to be searched. As you explore search results, you might need to navigate your code. Version contexts are respected by code intelligence hovers (go to definition and find references), and allow you to quickly traverse the specific code revisions you care about.++In this release, any non-master branches that are specified in the context will use our non-indexed search. This means that results may be slow for larger deployments. We are working on adding support for indexing additional branches that are specified within the context, and will include this in a future release.++To take advantage of of this feature, add a `versionContexts` block to the experimental features in your site configuration:++```json+"experimentalFeatures": [+ "versionContexts": [+ {+ "name": "srcgraph 3.16",+ "revisions": [+ {+ "repo": "github.com/sourcegraph/sourcegraph",+ "ref": "v3.16.0"+ },+ {+ "repo": "github.com/sourcegraph/zoekt",+ "ref": "b56036a3b745033badc48807bd67e91cd8d73bdf"+ }+ ]+ }+ ]+]+```++## Campaigns++<p class="container">+ <div style="padding:56.25% 0 0 0;position:relative;">+ <iframe src="https://www.youtube.com/embed/aqcCrqRB17w" style="position:absolute;top:0;left:0;width:100%;height:100%;" frameborder="0" webkitallowfullscreen="" mozallowfullscreen="" allowfullscreen=""></iframe>+ </div>+ <p style="text-align: center"><a href="https://youtu.be/aqcCrqRB17w" target="_blank">View on YouTube</a></p>+</p>++Campaign changeset usage counts including changesets created, added, and merged will be sent back in pings. [#10591](https://github.com/sourcegraph/sourcegraph/pull/10591)++## Best in class syntax highlighting++TODO: Erik is creating screenshots++We have made major improvements to syntax highlighting throughout Sourcegraph. In addition to general improvements, six new languages are supported (Smarty, Ethereum / Solidity / Vyper, Cuda, COBOL, vb.NET, and ASP.NET), and 30 new file extensions are now detected. ++Additionally, this release adds best-in-class syntax highlighting to code diffs. This richer view of diffs can easily be accessed from your pull request (or merge request) using the Sourcegraph browser extension by clicking on the Sourcegraph button in a file header. Alternatively, you can compare revisions directly from Sourcegraph by going to the compare section from a repository page. You can also see this in action on your [campaigns](#campaigns) to make changes across all the repositories at your organization. ++Take a look at the syntax highlighting on a diff that <WHAT IS THIS DIFF ABOUT> in the Sourcegraph repository.
Added GIF that transitions between light and dark mode Sourcegraph diffs
comment created time in 3 months
push eventsourcegraph/about
commit sha 2a47cfdccb4bcc32e2b460d6108650bdaa9042cc
Add 3.16 post to featured blog posts on the home page
commit sha 1875ffb1c110bb2826251bb2eba4dea18324886c
Syntax highlighting gif
push time in 3 months
push eventsourcegraph/about
commit sha 59e70ec7bab6413c30c6a1fc4ca41e241d19b4a0
Added version context search video
push time in 3 months
pull request commentsourcegraph/about
Did you mean to add the DismissableAlert component?
Also, the eWeek image is missing.
comment created time in 3 months
push eventsourcegraph/about
commit sha 0cc36cc2fed5529f91033c7379fb91694fefcd70
handbook: New page for creating screenshots, GIFs, and videos (#952) * handbook: New page for creating screenshots, GIFs, and videos * Minor edits * Update handbook/marketing/adding_screenshots_screen_recording.md Co-authored-by: aileenrose <aileenrose@users.noreply.github.com> * Update handbook/marketing/adding_screenshots_screen_recording.md Co-authored-by: Christina Forney <christina@sourcegraph.com> * Update handbook/marketing/adding_screenshots_screen_recording.md Co-authored-by: Christina Forney <christina@sourcegraph.com> * Update handbook/marketing/adding_screenshots_screen_recording.md Co-authored-by: Christina Forney <christina@sourcegraph.com> * Update handbook/marketing/adding_screenshots_screen_recording.md Co-authored-by: Christina Forney <christina@sourcegraph.com> * Update handbook/marketing/adding_screenshots_screen_recording.md Co-authored-by: aileenrose <aileenrose@users.noreply.github.com> * Clarified "no retina" and "1x" terminology * Added content for voice-overs and start and end screens Co-authored-by: aileenrose <aileenrose@users.noreply.github.com> Co-authored-by: Christina Forney <christina@sourcegraph.com>
push time in 3 months
pull request commentsourcegraph/about
handbook: New page for creating screenshots, GIFs, and videos
@christinaforney Also added content for voice-overs and start/end video screens.
comment created time in 3 months
push eventsourcegraph/about
commit sha 671d812dd1413471b188dc6077b298cef9c6d24f
Added content for voice-overs and start and end screens
push time in 3 months
Pull request review commentsourcegraph/about
handbook: New page for creating screenshots, GIFs, and videos
+# Adding a screenshot or screen recording (GIF and video)++> Note: This guide presumes macOS++## TL;DR++- Favor capturing only the part of the screen that’s required+- Keep GIFs 15 seconds or less+- GIFs are typically great for short "check this out" recordings, where videos are better at "how-to" or promotional style content+- Keep GIF and images as small as possible with no retina sizes (just 1 x)
Added explanation "(ratio of image size to intended display size is 1:1)"
comment created time in 3 months
push eventsourcegraph/about
commit sha 5978550488ac875cadae8651a0e6b913ae8fd104
Added content for voice-overs and start and end screens
push time in 3 months
push eventsourcegraph/about
commit sha 421cd2d8b047bcbf610ef84f6fb6bec6cf5c9a11
Clarified "no retina" and "1x" terminology
push time in 3 months
push eventsourcegraph/about
commit sha 9e31c8f8d4d285a00858108fc1c8f3116cfbc862
Update handbook/marketing/adding_screenshots_screen_recording.md Co-authored-by: aileenrose <aileenrose@users.noreply.github.com>
push time in 3 months
push eventsourcegraph/about
commit sha 42f8178017a65169b0d9e1a12f2e5798686dc0c6
Update handbook/marketing/adding_screenshots_screen_recording.md Co-authored-by: Christina Forney <christina@sourcegraph.com>
push time in 3 months