mcrt 1.11.0 → 1.12.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: aacbbeffea4e95a60206062e751fef40f010552b
-  data.tar.gz: 47156b150eb9c7826b4c4f57cbdaa68cd38820cf
+  metadata.gz: 18bfb01e87f43ed4a06150ddd28ba3af68bc9b33
+  data.tar.gz: 84b497ebe29495a52733303fa6853436137f0fc7
 SHA512:
-  metadata.gz: 011755fa8b3f2521b015454402e467a3a34f7b29ab498671817c24fee82e4e440db461bbffeb59c4daf29b28cd911074402e6bb7c11efebe4820e636ddcbad06
-  data.tar.gz: b75ffca4d58322e4d813e37e76261a0f5fa552c9d986fa94f4e302b2d6990d18d18cca0ed99478201bd5f9ef0f48943d93e7376c57190b6eb56b04e97212c780
+  metadata.gz: 8e777cea3fa9befe1d4ad81f33b841e8ccb4abae6aded4560734ec3496fc23ba7e2408770a157c538c55a833ed0b166d90c3a059309ae211c1775e27a07513b9
+  data.tar.gz: 56ed9f6f71932de75e40a5955c3c31302f001e5236ba27657bfffdb98d220a4eaaa85c2078bc19163f683edd7b8bdba52be48d52d28947452a678e64420c514b

data/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,45 @@
+<!--
+Thanks for your interest in the project. I appreciate bugs filed and PRs submitted!
+Please make sure that you are familiar with and follow the Code of Conduct for
+this project (found in the CODE_OF_CONDUCT.md file).
+
+Please fill out this template with all the relevant information so we can
+understand what's going on and fix the issue.
+
+I may ask you to submit the fix (after giving some direction).
+-->
+
+Environment:
+
+<!--
+  Please provide the version of this project where the issue occurred as well as the
+  versions of other environmental factors. This could be virtual machine version, os
+  version, browser version etc.
+-->
+
+Relevant code or config:
+
+```
+
+```
+
+What you did:
+
+
+
+What happened:
+
+<!-- Please provide the full error message/screenshots/anything -->
+
+Reproduction repository:
+
+<!--
+If possible, please create a repository that reproduces the issue with the
+minimal amount of code possible.
+-->
+
+Problem description:
+
+
+
+Suggested solution:

data/CONTRIBUTING.md

@@ -1,19 +1,34 @@
 # How to Contribute
 
-Pull requests are greatly appreciated and are what makes opensource great. Here's a quick guide:
+We'd love to accept your patches and contributions to this project. Pull requests are part of
+what makes open source great. There are just a few small guidelines you need to follow.
 
-* Fork it
-* Create your feature branch (`git checkout -b my-new-feature`)
-* Commit your changes (`git commit -am 'Add some feature'`)
-* Push to the branch (`git push origin my-new-feature`)
-* Create new Pull Request
+## Code of Conduct
 
-Pester us if we don't get your Pull Requests merged in a timely fashion. :)
+Participation in this project comes under the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md)
+
+## Submitting code via Pull Requests
+
+- We follow the [Github Pull Request Model](https://help.github.com/articles/about-pull-requests/) for
+  all contributions.
+- For large bodies of work, we recommend creating an issue outlining the feature that you wish to build,
+  and describing how it will be implemented. This gives a chance for review to happen early, and ensures
+  no wasted effort occurs.
+- All submissions, will require review before being merged.
+- Finally - *Thanks* for considering submitting code to the project!
+
+## Formatting
+
+When submitting pull requests, make sure to do the following:
+
+- Maintain the same code style as the rest of the project.
+- Remove trailing whitespace. Many editors will do this automatically.
+- Ensure any new files have [a trailing newline](https://stackoverflow.com/questions/5813311/no-newline-at-end-of-file)
 
 ## How to speed the merging of pull requests
 
-* Describe your changes in the CHANGELOG.
-* Give yourself some credit in the appropriate place (usually the CHANGELOG).
+* Describe your changes in the CHANGELOG.md (if present).
+* Give yourself some credit in the appropriate place (usually the CHANGELOG.md).
 * Make commits of logical units.
 * Ensure your commit messages help others understand what you are doing and why.
 * Check for unnecessary whitespace with `git diff --check` before committing.
@@ -23,4 +38,6 @@ Pester us if we don't get your Pull Requests merged in a timely fashion. :)
 ## Additional Resources
 
 * [General GitHub documentation](http://help.github.com/)
-* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
+* [How to write a good Git Commit message](https://chris.beams.io/posts/git-commit/) -
+  Great way to make sure your Pull Requests get accepted.
+* [An Open Source Etiquette Guidebook](https://css-tricks.com/open-source-etiquette-guidebook/#article-header-id-1)

data/lib/mcrt.rb

@@ -127,7 +127,7 @@ class MavenCentralReleaseTool
   def get_my_ip_addresses
     addresses = Socket.ip_address_list.collect {|a| a.ip_address.to_s}
     begin
-      addresses << Net::HTTP.get(URI('http://www.myexternalip.com/raw')).strip
+      addresses << `dig +short myip.opendns.com @resolver1.opendns.com`.strip
     rescue Exception
       # ignored
     end

data/mcrt.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |s|
   s.name               = %q{mcrt}
-  s.version            = '1.11.0'
+  s.version            = '1.12.0'
   s.platform           = Gem::Platform::RUBY
 
   s.authors            = ['Peter Donald']

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: mcrt
 version: !ruby/object:Gem::Version
-  version: 1.11.0
+  version: 1.12.0
 platform: ruby
 authors:
 - Peter Donald
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-05-22 00:00:00.000000000 Z
+date: 2018-10-08 00:00:00.000000000 Z
 dependencies: []
 description: Maven Central Release Tool.
 email: peter@realityforge.org
@@ -17,6 +17,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".gitattributes"
+- ".github/ISSUE_TEMPLATE.md"
 - ".gitignore"
 - ".ruby-version"
 - ".travis.yml"