test_with 0.1.1 → 0.1.2

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: d3c31c926eb38ddc3363321947ba0961439cc0a9
4
- data.tar.gz: 0da0e4fc2927538d4747961725781148a2010256
3
+ metadata.gz: f4788fb003d119affbb528d2e095ef6ec71731e8
4
+ data.tar.gz: 12819698fd1695262a0da1187e72107078b20cf9
5
5
  SHA512:
6
- metadata.gz: 80035c428ad2fa9927a98f447f5a1ca3785f61877b8e3e59c8c541eb8298064af58c5e741205ab699819863de7f18735fbf76016a0f4c68c88d23b033181a360
7
- data.tar.gz: c207a793ebb380f7dc4d899f9864b53bd50debf8ec21ac76e6be941003b43b67da442dc3c1c924fa0da2675bc106f4fce838ad30c76ec577928dd2fcccd9ff4d
6
+ metadata.gz: 9212281cfc9edc46d062ed31f3d463b41f3eb4e3c8355a77e8a53eaac9920e4ce1338ce505224e895f5b2b0540fcc610146f99372fc4092af72bd8e5fa5a89ba
7
+ data.tar.gz: c14c7f7ae14193cded1a7c448f3d9711a3909e44a87ce954f3e8ead444b85d127980f2d13a191f6ee341f9e463315cd9d68cf58210c3eb99b1bdeb06675ebf2c
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- test_with (0.1.1)
4
+ test_with (0.1.2)
5
5
  listen
6
6
 
7
7
  GEM
data/README.md CHANGED
@@ -1,43 +1,25 @@
1
- # TestWith
1
+ test-with **watches your current directory and runs the command you specify every time something is changed. I find it valuable because...**
2
2
 
3
- Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/test_with`. To experiment with that code, run `bin/console` for an interactive prompt.
3
+ `test-with truffle test` will run the test suite of your Ethereum app and update the results after every file change
4
4
 
5
- TODO: Delete this and the text above, and describe your gem
5
+ `test-with rails test` will run the test suite of your Rails app and update the results after every file change
6
6
 
7
- ## Installation
8
-
9
- Add this line to your application's Gemfile:
10
-
11
- ```ruby
12
- gem 'test_with'
13
- ```
7
+ `test-with rails test test/controllers/charges_controller.rb` will run the specified Rails test and update the results after every file change
14
8
 
15
- And then execute:
9
+ `test-with ruby letter_test.rb` will run the specified Ruby file and update the results after every file change
16
10
 
17
- $ bundle
11
+ `test-with git status` will show you list of changes in the directory, updated in real time
18
12
 
19
- Or install it yourself as:
13
+ ## Installation
20
14
 
21
- $ gem install test_with
15
+ Run in your terminal
22
16
 
17
+ gem install test_with
18
+
23
19
  ## Usage
24
20
 
25
- TODO: Write usage instructions here
26
-
27
- ## Development
28
-
29
- After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
30
-
31
- To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
32
-
33
- ## Contributing
34
-
35
- Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/test_with. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
21
+ See above, the very top.
36
22
 
37
23
  ## License
38
24
 
39
25
  The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
40
-
41
- ## Code of Conduct
42
-
43
- Everyone interacting in the TestWith project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/test_with/blob/master/CODE_OF_CONDUCT.md).
data/test_with.gemspec CHANGED
@@ -4,13 +4,13 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
4
4
 
5
5
  Gem::Specification.new do |spec|
6
6
  spec.name = "test_with"
7
- spec.version = "0.1.1"
7
+ spec.version = "0.1.2"
8
8
  spec.authors = ["Anton Khamets"]
9
9
  spec.email = ["colorfulfool@gmail.com"]
10
10
 
11
11
  spec.summary = "Watches current dir and runs the command after any change"
12
12
  spec.description = "A generalization if autotest: watches current dir and runs the command after any change"
13
- # spec.homepage = "TODO: Put your gem's website or public repo URL here."
13
+ spec.homepage = "https://github.com/colorfulfool/test_with"
14
14
  spec.license = "MIT"
15
15
 
16
16
  spec.files = `git ls-files -z`.split("\x0").reject do |f|
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: test_with
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.1
4
+ version: 0.1.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Anton Khamets
@@ -63,7 +63,6 @@ extensions: []
63
63
  extra_rdoc_files: []
64
64
  files:
65
65
  - ".gitignore"
66
- - CODE_OF_CONDUCT.md
67
66
  - Gemfile
68
67
  - Gemfile.lock
69
68
  - LICENSE.txt
@@ -72,7 +71,7 @@ files:
72
71
  - bin/setup
73
72
  - bin/test-with
74
73
  - test_with.gemspec
75
- homepage:
74
+ homepage: https://github.com/colorfulfool/test_with
76
75
  licenses:
77
76
  - MIT
78
77
  metadata: {}
data/CODE_OF_CONDUCT.md DELETED
@@ -1,74 +0,0 @@
1
- # Contributor Covenant Code of Conduct
2
-
3
- ## Our Pledge
4
-
5
- In the interest of fostering an open and welcoming environment, we as
6
- contributors and maintainers pledge to making participation in our project and
7
- our community a harassment-free experience for everyone, regardless of age, body
8
- size, disability, ethnicity, gender identity and expression, level of experience,
9
- nationality, personal appearance, race, religion, or sexual identity and
10
- orientation.
11
-
12
- ## Our Standards
13
-
14
- Examples of behavior that contributes to creating a positive environment
15
- include:
16
-
17
- * Using welcoming and inclusive language
18
- * Being respectful of differing viewpoints and experiences
19
- * Gracefully accepting constructive criticism
20
- * Focusing on what is best for the community
21
- * Showing empathy towards other community members
22
-
23
- Examples of unacceptable behavior by participants include:
24
-
25
- * The use of sexualized language or imagery and unwelcome sexual attention or
26
- advances
27
- * Trolling, insulting/derogatory comments, and personal or political attacks
28
- * Public or private harassment
29
- * Publishing others' private information, such as a physical or electronic
30
- address, without explicit permission
31
- * Other conduct which could reasonably be considered inappropriate in a
32
- professional setting
33
-
34
- ## Our Responsibilities
35
-
36
- Project maintainers are responsible for clarifying the standards of acceptable
37
- behavior and are expected to take appropriate and fair corrective action in
38
- response to any instances of unacceptable behavior.
39
-
40
- Project maintainers have the right and responsibility to remove, edit, or
41
- reject comments, commits, code, wiki edits, issues, and other contributions
42
- that are not aligned to this Code of Conduct, or to ban temporarily or
43
- permanently any contributor for other behaviors that they deem inappropriate,
44
- threatening, offensive, or harmful.
45
-
46
- ## Scope
47
-
48
- This Code of Conduct applies both within project spaces and in public spaces
49
- when an individual is representing the project or its community. Examples of
50
- representing a project or community include using an official project e-mail
51
- address, posting via an official social media account, or acting as an appointed
52
- representative at an online or offline event. Representation of a project may be
53
- further defined and clarified by project maintainers.
54
-
55
- ## Enforcement
56
-
57
- Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
- reported by contacting the project team at t0ny.hamster@gmail.com. All
59
- complaints will be reviewed and investigated and will result in a response that
60
- is deemed necessary and appropriate to the circumstances. The project team is
61
- obligated to maintain confidentiality with regard to the reporter of an incident.
62
- Further details of specific enforcement policies may be posted separately.
63
-
64
- Project maintainers who do not follow or enforce the Code of Conduct in good
65
- faith may face temporary or permanent repercussions as determined by other
66
- members of the project's leadership.
67
-
68
- ## Attribution
69
-
70
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
- available at [http://contributor-covenant.org/version/1/4][version]
72
-
73
- [homepage]: http://contributor-covenant.org
74
- [version]: http://contributor-covenant.org/version/1/4/