4 ms·

I'm almost certain that's a bot. See https://github.com/sunlightlabs/us-laws/issues/135 https://github.com/sunlightlabs/us-laws/issues/135

• jey 12y ago
  And it reveals a complete misunderstanding/misuse of GitHub Issues: the issue is filed after the law has been passed and signed into effect, so the issue is "opened" only after we would have closed the issue, and it appears that it will never get closed.
  • apendleton 12y ago
    Sunlighter here (though this isn't my project). This was mostly done to test our IFTTT channel (https://ifttt.com/sunlightfoundation https://ifttt.com/sunlightfoundation), so I think we were limited in terms of what actions we could trigger. We've talked about doing a non-IFTTT version that would extend the metaphor way further, but haven't (yet) actually made it happen.
  • iancarroll 12y ago
    It's not intended to provide a medium of discussion (at least pre-vote) - it's intended to be a directory of laws. I would assume Issues is only used for IFTTT compatibility.
  • pan69 12y ago
    Sorry, I don't understand what you're saying, are you implying that once a feature (law) has been pushed into production (signed off) there can be no issues filed against such feature?
    • skndr 12y ago
      For this analogy, a bill should actually be a pull request and a signed law is a merged request. I think the problem is that an 'issue' should be a proposal, a bug report, etc. In this case, none of the 'issues' being created are intended to be closed.