Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 19 14:09
    andrew closed #853
  • Oct 19 14:09
    andrew closed #715
  • Oct 19 14:09
    andrew closed #714
  • Oct 19 14:09
    andrew closed #444
  • Oct 19 14:09
    andrew closed #417
  • Oct 19 14:09
    andrew closed #71
  • Oct 19 14:09
    andrew closed #57
  • Oct 19 14:09
    andrew closed #70
  • Oct 19 14:09
    andrew closed #23
  • Oct 19 14:09
    andrew closed #59
  • Oct 19 14:09
    andrew closed #58
  • Oct 19 14:08
    andrew closed #41
  • Oct 19 14:08
    andrew closed #22
  • Oct 19 14:08
    andrew closed #19
  • Oct 19 14:08

    dependabot-preview[bot] on bundler

    (compare)

  • Oct 19 14:08

    andrew on master

    Bump webmock from 3.9.2 to 3.9.… Merge pull request #1300 from 2… (compare)

  • Oct 19 14:08
    andrew closed #1300
  • Oct 19 14:08

    dependabot-preview[bot] on bundler

    (compare)

  • Oct 19 14:08

    andrew on master

    Bump faraday from 1.0.1 to 1.1.… Merge pull request #1299 from 2… (compare)

  • Oct 19 14:08
    andrew closed #1299
Mordechai Zuber
@M-Zuber
blob
This message was deleted
methinks this is a little high as the repo shows
blob
And 19 closed PR's
Mordechai Zuber
@M-Zuber
Would love to have a meeting of the minds to see if/how contribulator and forkability can work together/ learn from each other
Andrew Nesbitt
@andrew
That would be great, a lot of the ideas of contribulator have also gone into libraries.io at a much bigger scale
Mordechai Zuber
@M-Zuber
Do you consider libraries.io a succesor or do the two have different use cases in your mind?
I'm asking as I don't see an obvious way to get forkability involved in libraries.io, but I do see the data being a nice side fact for contribultor
meaning if I have a high contribultor score , but something like no commented issues is making me fail forkability,
that should indicate that it is a nice project, but it might be hard to actually get somewhere
not sure though how it could be used with libraries.io though
Andrew Nesbitt
@andrew
I'm not actively working on contribulator, but was thinking of using it to help with suggestions for 24pr
forkability could do that too
Mordechai Zuber
@M-Zuber
that would be cool for us, but i would assume it's much easier to add contribulator as its in ruby
Andrew Nesbitt
@andrew
Would just be pulling in some data over an API, rather than building the functionality into 24pr directly
Mordechai Zuber
@M-Zuber
I don't know ruby, and was thinking to build it an simply to not have to rely on GH pages being available
(gitter app spell check doesn't work.... ARGHHH)
Andrew Nesbitt
@andrew
We can cache the result to make it resilient to downtime
Definitely worth opening some issues to discuss it further
loads of people will be around to help after December 1st
Mordechai Zuber
@M-Zuber
:laughing:
I guess I have to learn ruby :smile:
Probably will also have to make changes to forkability if thats whats used (just another endpoint to the api I think)
24pullrequests/24pullrequests#987
Al Snow
@jasnow
@andrew - Can you add definition of [homepage, Contributing, Changelog, Code of conduct] for contribulator tool? Try the tool on one of my repos and did not know how to get "true" for each of these checks.
Andrew Nesbitt
@andrew
I’ve not been actively working on contributor recently
Al Snow
@jasnow
ok
Al Snow
@jasnow
You can close #82, #83, #86, #90, #92. Also #88's gem number is lower than lock file so that can be closed. #93 is blocked by another gem - FYI.
Peter Mellett
@wadtech
@jasnow could you comment on #93 to explain that? Cheers
Al Snow
@jasnow
@wadtech - Added comment as requested.
Peter Mellett
@wadtech
:+1: cheers
Al Snow
@jasnow
@andrew - Why was #95 not merged?
Andrew Nesbitt
@andrew
I updated a couple gems and it included that one
Al Snow
@jasnow
ok
Al Snow
@jasnow
@andrew - https://libraries.io/ is down (getting "Application Error")
Andrew Nesbitt
@andrew
@jasnow yeah it’s having a little blip, should be back soon
Al Snow
@jasnow
ok
Ghost
@ghost~55a04b725e0d51bd787af54c
Test
Peter Mellett
@wadtech
👋
Ryan L McIntyre
@ryanoasis
:wave: