-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP Configure Satis repository when enabling extension #21
Conversation
…ser, fixed tests, added travis
This makes it easier to re-use in other places of the extension
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you combine the changes I did in the satis
branch on top of yours? Eg the travis-ci config.
See the changes
Didn't notice your I will try to merge all this in a single PR |
Codecov Report
@@ Coverage Diff @@
## master #21 +/- ##
=========================================
Coverage ? 31.73%
=========================================
Files ? 29
Lines ? 460
Branches ? 0
=========================================
Hits ? 146
Misses ? 314
Partials ? 0
Continue to review full report at Codecov.
|
Confirmed that this only works if "repositories" is an object, not an array, we have to mutate all items in that list to become an object (perhaps based on the path?) |
fixed the 403 by putting the token and Bearer witin single quotes |
Going to add further logic in a new branch, let's move on with this. |
It's not working at the moment, I'm getting 403 errors from the satis endpoint when enabled :(
Also, there's a quiet issue if a "repositories" key is present in composer.json but uses an array instead of an object (we need to name our repo so it can be easily found & replaced when enabling the extension)