chicago
Here are 113 public repositories matching this topic...
The major.minor.patch concept is clear, but what does the part after the dash indicate?
I believe it's one of these:
- major.minor.patch-commit
- major.minor.patch-buildnumber
It's to me what convention @tomschenkjr was using. I see some big numbers which would seem like commits, but I know that the CRAN submission process can be challenging and it could be actual builds.
Either wa
-
Updated
Aug 25, 2015
-
Updated
Aug 3, 2015 - R
As a ChiPy attendee, I want to see upcoming meetings on the homepage sooner after the previous meeting has passed, so I'm not seeing past events.
The day after the main ChiPy meeting, I'm still seeing the previous meeting's post. This is because we provide a 24 hour grace period to allow a meeting to still show up even after the event has passed its start time. Reasonably, however, 24 hours is
-
Updated
Aug 15, 2015 - R
-
Updated
Sep 17, 2018 - R
-
Updated
Jun 15, 2020 - Kotlin
-
Updated
Feb 27, 2020 - HTML
-
Updated
Aug 3, 2015 - R
Let's discuss what's different about developing smart contracts for Ethereum using Solidity v0.5.x. (Newcomers to Solidity are welcome too, though!)
Added a LICENSE.md and NOTICE.md file. The NOTICE file needs to mention the licenses of:
- Libraries used in the template
- Images and icons used
It looks like bills that should be marked as passed, are instead being flagged as stale:
There are no bills marked as passed in the status search facet:
Here's a bill that shows the stale status, but has been passed in the ac
-
Updated
May 31, 2020 - Python
-
Updated
Jun 25, 2019 - Shell
-
Updated
Aug 8, 2017
-
Updated
Nov 8, 2019 - HTML
-
Updated
Jun 20, 2018 - Ruby
-
Updated
Nov 12, 2018 - JavaScript
-
Updated
Feb 20, 2019 - CSS
-
Updated
May 26, 2020 - JavaScript
-
Updated
Oct 4, 2018 - Python
Improve this page
Add a description, image, and links to the chicago topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the chicago topic, visit your repo's landing page and select "manage topics."


The report only sources the 30 file, but datTest is created in 31. As a result the report should be updated to source both files to ensure it works in a standalone fashion: