octokit / fixtures Goto Github PK
View Code? Open in Web Editor NEWFixtures for all the octokittens
License: MIT License
Fixtures for all the octokittens
License: MIT License
Hi there! I'd love to use some of the boilerplate from this module to test my own wrapper of https://github.com/octokit/node-github. Would you be interested in a PR that allowed me to supply scenarios & fixtures from the caller?
2.9.0
to 2.10.0
.This version is covered by your current version range and after updating it in your project the build failed.
bottleneck is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
done()
method which returns the total weight of completed jobs across the Cluster.reservoirRefreshInterval
, the reservoir
value is automatically reset to reservoirRefreshAmount
.The new version differs by 19 commits.
20a9cf4
2.10.0
7a745d6
Updated README and typings for v2.10.0
af68723
Redis Cluster optimizations
e7ead7b
Implemented reservoir refresh
2dd4093
incrementReservoir now returns the new value
1c8168a
Added heartbeat
da73245
Refactor Lua 'now' value, fix minor race condition
29b5cae
Refactor of the 'capacity' internals
9f67c64
Removed CS header
9b73a24
Added basic migration system
7cd1cc7
More tests and improvements to Clustering
cc4c0fd
Fixed race condition in Clustering
6d3cbf7
Clear lost jobs at connection
92f6d62
Redis memory optimization, test improvements
cb6b7bb
Small refactor of Redis connections
There are 19 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
We currently calculate and set the response Content-Length
header after normalization
fixtures/lib/normalize/index.js
Line 77 in 42798d0
Some endpoints respond with with Transfer-Encoding: chunked
though, e.g. for the upload asset endpoint
fixtures/scenarios/api.github.com/release-assets/normalized-fixture.json
Lines 121 to 139 in 42798d0
The problem is that having both Transfer-Encoding
and Content-Length
headers is invalid per HTTP 1.1 definition, see request/request#2091
nock seems to ignore that fact, but when using the fixtures to create server response in express, the server returns an HPE_UNEXPECTED_CONTENT_LENGTH
error.
Ideally nock would have full support for streamed responses using Chunked Transfer Encoding, but for the time being I would remove the Transfer-Encoding
header entirely as part of our normalization
I discussed with @kytrinyx that the repositories we create with the fixtures accounts and on the fixtures organization are all to be used read-only. For scenarios that need write operations, temporary repositories should be created.
I’ll make a follow up PR for #16 to create a temporary repository the "add and remove repository collaborators" test
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | nock |
Current Version | 9.2.4 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
nock is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 1 commits.
11f1a25
fix: remove arrow functions to restore Node<4 compatibility (#1114)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | semantic-release |
Current Version | 15.6.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 1 commits.
d4f68a5
fix(package): update yargs to version 12.0.0
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | envalid |
Current Version | 4.1.3 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
envalid is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | humanize-string |
Current Version | 1.0.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
humanize-string is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | tar-stream |
Current Version | 1.5.7 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
tar-stream is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 3 commits.
59abdc8
1.6.0
105192d
tweak #83
689d3fa
Trigger an error if there is an incomplete entry at the end of stream (#83)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | standard |
Current Version | 11.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
standard is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 20 commits.
670a3be
authors
b7e6cbc
11.0.1
34a3c40
Merge pull request #1092 from watson/elastic-logo
5382643
Replace Opbeat with Elastic logo
c40c799
Merge pull request #1091 from mackermans/master
504fcff
docs(README): update typeform logo
a5b779f
Swap README.md and RULES.md symlinks (#1090)
e818224
Merge pull request #1072 from standard/greenkeeper/eslint-plugin-react-7.7.0
9dc888f
Merge branch 'master' into greenkeeper/eslint-plugin-react-7.7.0
a5293dd
Merge pull request #1075 from standard/greenkeeper/eslint-plugin-import-2.9.0
ebf6620
Merge pull request #1087 from standard/greenkeeper/eslint-plugin-promise-3.7.0
116a871
fix(package): update eslint-plugin-promise to version 3.7.0
738edc4
readme: add standard talk
c93ac0d
Merge pull request #1076 from tumobi/fix-links
4f8c1f5
Fix webstorm.md links
There are 20 commits in total.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
part of #14
see octokit/octokit.js#603 for reference
part of #14
While at it, I’ll create a reference, get a reference, update a reference and delete a reference:
https://developer.github.com/v3/git/refs/
Branch | Build failing 🚨 |
---|---|
Dependency |
semantic-release
|
Current Version | 15.5.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 1 commits.
29e7ebf
fix(package): update hook-std to version 1.0.0
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | glob |
Current Version | 7.1.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
glob is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | nock |
Current Version | 9.4.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
nock is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 2 commits.
5aa1081
docs: Add CONTRIBUTE, edit README, update LICENSE year (#1155)
f81fb6d
fix: request overrider checks req.headers to parse body as JSON (#1157)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
based on the GraphQL Schema I'd assume conflicting
, mergeable
and unknown
https://github.com/gr2m/github-graphql-schema/blob/e44088a5b93affc8a28a4e34a6049f62cc6583f2/schema.graphql#L2877-L2886
More context:
octokit/octokit.rb#626
google/go-github#820 (comment)
https://platform.github.community/t/documentation-about-mergeable-state/4259
/cc @ryangribble (edit comment for more details)
Branch | Build failing 🚨 |
---|---|
Dependency | bottleneck |
Current Version | 2.7.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
bottleneck is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
part of #14
There's a README.md section on using the standalone mock server, and giving a curl command as an example:
curl -H'Accept: application/vnd.github.v3+json' http://localhost:3000/repos/octocat/hello-world
I noticed the fixtures don't use octocat
as the organization, and that should probably be fixed in the curl command example. Additionally, though, I can't seem to actually test the standalone server using node-github:
'use strict';
const GitHubApi = require('github');
const github = new GitHubApi({ host: 'localhost', port: 3000, protocol: 'http' });
github.repos.get({ owner: 'octokit-fixture-org', repo: 'hello-world' });
This fails even when the curl succeeds:
"error": "Nock: No match for request",
"request": {
"method": "GET",
"url": "https://api.github.com/repos/octokit-fixture-org/hello-world",
"headers": {
"connection": "close",
"accept": "application/vnd.github.drax-preview+json",
"user-agent": "NodeJS HTTP Client",
"content-length": "0",
"host": "api.github.com"
}
}
}
Is there some trick to setup the library to use the standalone server? I'm happy to PR additional documentation if you could steer me to the right usage. Thanks in advance!
Branch | Build failing 🚨 |
---|---|
Dependency | bottleneck |
Current Version | 2.8.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
bottleneck is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
publish()
method and listen to the message
event on a limiter.ready()
promise to complete before issuing commands. The commands will be queued until the limiter successfully connects. Make sure to listen to the error
event to handle connection errors.jobs()
method to return a list of job ids in a specific state.check()
) when a Group key is recreated after timing out.The new version differs by 9 commits.
1a7ec8d
2.9.0
ad5b998
Minor IORedis refactor
c36e86d
Added jobs()
f2646d3
ready() improvements
ac1afc2
Optimized Redis connections for large Groups
71327b3
Added pubsub and tests
ca84e77
Updated Redis connection setup
f9865eb
Updated CS to 2.3.x
0491071
Updated README.md
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
the cron job currently just updates normalized fixtures if it finds any differences.
fixtures/lib/notify-about-fixtures-changes.js
Lines 119 to 155 in 49f9389
Because of that, the CI will break, as the integration test run normalization on all raw fixtures and compare the outcome to the normalized fixtures
4.17.10
to 4.17.11
.This version is covered by your current version range and after updating it in your project the build failed.
lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
@gr2m What I am trying to figure out is how to version control a new scenario if it is not included in @octokit/fixtures.
In the next couple weeks, I will be writing several new scenarios for https://github.com/node-gh/gh/. Would you recommend including your repo in my project to create new scenarios or just send you a PR with the new scenarios?
By the way I am learning a lot from this project. Fantastic work!
0.5.2
to 0.5.3
.This version is covered by your current version range and after updating it in your project the build failed.
json-diff is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 11 commits ahead by 11, behind by 1.
6061203
Version bump to 0.5.3
90ea717
Typo fix
401e561
Commit package-lock.json
7c972bd
npm scripts already have node_modules bins in PATH
2d5224c
Merge pull request #29 from queicherius/master
fb642d5
Merge pull request #30 from worldsayshi/patch-1
b5ff6e9
Merge pull request #33 from rustydevs/master
ed36130
Update README.md
913b12b
Documenting usage in javascript
66ea81c
Documenting usage in javascript
c0b3593
Fix behaviour for "null" values
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency |
[semantic-release](https://github.com/semantic-release/semantic-release)
|
Current Version | 15.5.5 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 1 commits.
4454d57
feat: allow to disable the publish plugin hook
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency |
nock
|
Current Version | 9.2.5 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
nock is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 5 commits.
2676fed
fix: match HTTP headers with case insensitivity (#1122)
8ce5be8
test: temporary disable test depending on external hosts
5977cdf
test: remove airplane mode from '(re-)activate after restore'
704eb25
Follow up on previous test
3111dce
test: remove airplane mode from 'allow unmocked option works'
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | nock |
Current Version | 9.1.6 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
nock is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 5 commits.
f3f8f0f
test: remove browserify tests
7cd752f
build(package): -browserify, zombie, node-static
68df807
test: https://example.org/unmocked
no longer returns default page
8fd0942
fix: case insensitive reply headers (#862)
797c518
docs(README): add extra warning about recording disabling mocks (#1053)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
it’s the only route which expects the raw text to be formatted instead of JSON, I need that for test coverage in node-github
:)
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.travis.yml
If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.
Greenkeeper has checked the engines
key in any package.json
file, the .nvmrc
file, and the .travis.yml
file, if present.
engines
was only updated if it defined a single version, not a range..nvmrc
was updated to Node.js 10.travis.yml
was only changed if there was a root-level node_js
that didn’t already include Node.js 10, such as node
or lts/*
. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.For many simpler .travis.yml
configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
in preparation for octokit/octokit.js#638
Branch | Build failing 🚨 |
---|---|
Dependency |
tar-stream
|
Current Version | 1.6.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
tar-stream is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
follow up for #5. Update CONTRIBUTING.md
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | semantic-release |
Current Version | 15.1.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 3 commits.
30ee231
fix: prevent git prompt before permissions verification
3c46455
fix: remove execa
timeout
dff0a34
docs: add "Introduction to Semantic Release" article
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | bottleneck |
Current Version | 2.7.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
bottleneck is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
{ datastore: "ioredis" }
. ioredis supports Redis Cluster and Redis Sentinel{ datastore: "redis", clusterNodes: [nodes] }
. See the ioredis cluster docs and the Bottleneck docs for more informationThe new version differs by 5 commits.
8d74e1a
2.8.0
967ce90
Small code cleanups
e7d9fe4
Redis Cluster support
d8aef84
Redis datastore refactor
694289b
First pass at IORedis support
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | semantic-release |
Current Version | 15.6.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 2 commits.
4abda31
fix: add debug log for git fetch
command
3602716
docs: update semantic-release
and travis-deploy-once
versions in examples
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
follow up for octokit/octokit.js#345
part of #14
part of #14
It looks like all builds on travis are sharing the same request limit across all builds, which it looks like it runs out of pretty quickly. That is a problem because we have to record requests that are unauthenticated for our fixtures.
Without any workaround, we will never get the record task to work: https://travis-ci.org/gr2m/octokit-fixtures/jobs/271878092#L461
If you don’t want to get notifications from this repository but would like to stay up-to-date, you can subscribe to this issue to only get the most critical updates.
this is in preparation for https://github.com/octokit/rest.js/issues/688
Branch | Build failing 🚨 |
---|---|
Dependency | nock |
Current Version | 9.4.1 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
nock is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 1 commits.
7fd2329
fix: Replaced util._extend with Object.assign due to deprecated since node v6.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | nock |
Current Version | 9.3.3 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
nock is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 4 commits.
e15820a
feat: emit 'request' event with body as third parameter (#1062)
a1fff39
build(package): update eslint to version 5.0.0 (#1151)
da5de6a
test: local ssl server (#1126)
e8479aa
docs: change url to match new GitHub address
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
See https://github.com/mikedeboer/node-github/tree/master/examples
Follow instructions at https://github.com/octokit/fixtures#updating-fixtures to create new fixtures
If you want to work on one of the issues, please create a new issue on this repository like #59, I’ll then update the list below to avoid multiple folks working on the same scenario :) After creating the issue, please send me a dm on twitter with a link to your issue, I’ll then provide you with the tokens that you need to record the scenarios with our fixture GitHub accounts
Make sure to read CONTRIBUTING.md and HOW_IT_WORKS.md, the latter has a linked screencast you can follow :)
part of #14
Branch | Build failing 🚨 |
---|---|
Dependency | bottleneck |
Current Version | 2.5.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
bottleneck is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency |
semantic-release
|
Current Version | 15.5.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 6 commits.
6a36832
fix(plugin-load): clarify load message
4d47b20
docs: clarify config file format
ddcf29a
chore(package): update nyc to version 12.0.1
4c157f3
docs(plugins): add semantic-release-vsce
c6636ab
docs(plugins): remove warning
44fd7fe
chore(package): update delay to version 3.0.0
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.