part of #14

this is in preparation for https://github.com/octokit/rest.js/issues/688

@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!

Version 9.4.1 of nock was just published.

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.

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 :)

• addCollaborator.js (#16)
• addLabelsToIssue.js (#25)
• createFile.js (#32)
• createStatus.js (#35)
• getContent.js (#42)
• getFollowers.js / getFollowing.js
• getStarred.js
• getIssuesForRepo.js
• getOrg.js (#8)
• getOrgPublicMembers.js
• getOutsideCollaborators.js
• getPullRequestReview.js / getPullRequestReviews.js
• getRawBlob.js
• getReactionsForIssue.js
• getReference.js (#47)
• getReferences.js (#47)
• getReleaseAsset.js
• getRepos.js
• getTimeline.js
• getUser.js
• getUserById.js
• getUserOrgs.js
• listOrgs.js
• lockIssue.js (#60)
• removeAssigneesFromIssue.js
• renderMarkdown.js (#78)
• searchIssues.js (#79)
• searchMostStarredRepos.js
• updateBranchProtection.js (#53)
• updateLabel.js (#50)
• updateReference.js (#47)

Version 15.6.2 of semantic-release was just published.

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.

Your Greenkeeper Bot 🌴

Version 2.7.2 of bottleneck was just published.

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.

Your Greenkeeper Bot 🌴

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

Version 2.9.0 of bottleneck was just published.

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.

Your Greenkeeper Bot 🌴

Version 1.6.1 of tar-stream was just published.

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.

Your Greenkeeper Bot 🌴

The devDependency bottleneck was updated from 2.9.0 to 2.10.0.

🚨 View failing branch.

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.

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .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.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 15.1.3 of semantic-release was just published.

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.

Your Greenkeeper Bot 🌴

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

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 9.2.5 of nock was just published.

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.

Your Greenkeeper Bot 🌴

follow up for #5. Update CONTRIBUTING.md

• list labels
• create label
• update label
• delete a label

Version 4.1.4 of envalid was just published.

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.

Your Greenkeeper Bot 🌴

Version 9.1.7 of nock was just published.

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.

Your Greenkeeper Bot 🌴

in preparation for octokit/octokit.js#638

Version 15.5.1 of semantic-release was just published.

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.

Your Greenkeeper Bot 🌴

Version 15.6.0 of semantic-release was just published.

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.

Your Greenkeeper Bot 🌴

follow up for octokit/octokit.js#345

Version 9.2.6 of nock was just published.

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.

Your Greenkeeper Bot 🌴

part of #14

Version 2.8.0 of bottleneck was just published.

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.

Your Greenkeeper Bot 🌴

Version 7.1.3 of glob was just published.

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.

Your Greenkeeper Bot 🌴

see octokit/octokit.js#603 for reference

Version 15.5.2 of semantic-release was just published.

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.

Your Greenkeeper Bot 🌴

Version 1.6.0 of tar-stream was just published.

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.

Your Greenkeeper Bot 🌴

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/

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 :)

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?

We currently calculate and set the response Content-Length header after normalization

Some endpoints respond with with Transfer-Encoding: chunked though, e.g. for the upload asset endpoint

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

Version 15.6.1 of semantic-release was just published.

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.

Your Greenkeeper Bot 🌴

the cron job currently just updates normalized fixtures if it finds any differences.

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

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.

Version 9.4.2 of nock was just published.

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.

Your Greenkeeper Bot 🌴

Version 9.4.0 of nock was just published.

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.

Your Greenkeeper Bot 🌴

The dependency lodash was updated from 4.17.10 to 4.17.11.

🚨 View failing branch.

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.

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)

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!

part of #14

The dependency json-diff was updated from 0.5.2 to 0.5.3.

🚨 View failing branch.

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.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 11.0.1 of standard was just published.

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.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.0.2 of humanize-string was just published.

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.

Your Greenkeeper Bot 🌴

part of #14

Version 2.5.1 of bottleneck was just published.

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.

Your Greenkeeper Bot 🌴

Problem is

JSON.stringify('').length
// 2

part of #14