| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
This will allow you to run `mocha -w` without any other special arguments and still get babel compilation
|
Looks like the mikedeboertest/TestRepo has been deleted which is why a number of the tests are broken. Does anyone know why that repo was deleted? |
Sorry, something went wrong.
|
I recreated the repo for that test user account |
Sorry, something went wrong.
|
Ok, I got hit with a 403 rate limited for the mikedeboertest account. So, I'll need to wait for that rate limit to go down before I can try again. |
Sorry, something went wrong.
|
I got the tests passing here: |
Sorry, something went wrong.
|
@mathieudutour Instead of pushing yet another fork and another module pushed up to npm I'd much rather see #263 happen and just get more people to work together. @michael What is holding this up from getting more people to help with it? I can so two active forks of this project and I'd really hate to side step the team that originally put this promised based wrapper together. |
Sorry, something went wrong.
|
Indeed, I'd be happy to help. (I published my fork because I needed some of the opened PRs for a project.) |
Sorry, something went wrong.
|
great, well I'll reach out and see if we can get the repo moved. |
Sorry, something went wrong.
…tRepo to get deleted.
|
The Issue tests should be fixed now. Still have 10 more failing tests |
Sorry, something went wrong.
|
Nevermind, something is still deleting that repo... |
Sorry, something went wrong.
|
I removed the dependency to that repo in my fork. I'll create a PR soon but there will be lots of changes. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
May I suggest that you migrate this repo to an organization and institute protected branch support on master so PRs cannot be merged when the CI is failing?
See: #263