ghedsh 1.1.40 → 2.3.8

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: c64f6b3a212a113c203031a57ee86bed73545e1b
4
- data.tar.gz: b4523ad22001791403763cee8b8fef349786e713
3
+ metadata.gz: 8ff77e682f54ee1c02b5d816112c73b4a543213d
4
+ data.tar.gz: 8cf4004829bb638a8763363108c6470ab50c9ae5
5
5
  SHA512:
6
- metadata.gz: 561817bf58d181b357cd06136aad98fa2d9e6dd498077614fe0d97b3d2b8bd91b6ba2c301a46a0e8d3d1b2cc73dd29b81c1feed6ca732e577bbb7731b41b78c8
7
- data.tar.gz: d8ddd86623e67fff0207b00ea31344a325efff96663d9d517637f8243ac00d1d9c51808228575328a6a8514a5f1429164e09f8b91f1843b01f12b980eb3ca3b0
6
+ metadata.gz: 0ea8c7e4b4f3d08d614e1372b26fe5def323dfe55745dec87b1ae59a9376cbfe6db88da51ee4b6015fbfee6eb3d07ad571d8103547c28f25b0db4373313e689e
7
+ data.tar.gz: e689b0832972ece3c26a27d3e4c2f0e8727b1ef2e0df9044e37dc83635dab478eb7c80ce16006f4008b83ff82a992d1e05d8611b5d952e6a50a5971734dc0c7e
data/.editorconfig ADDED
@@ -0,0 +1,12 @@
1
+ root = true
2
+
3
+ [*]
4
+ indent_style = space
5
+ indent_size = 2
6
+ end_of_line = lf
7
+ charset = utf-8
8
+ trim_trailing_whitespace = true
9
+ insert_final_newline = true
10
+
11
+ [*.md]
12
+ trim_trailing_whitespace = false
@@ -0,0 +1,31 @@
1
+ <!--- Provide a general summary of the issue in the Title above -->
2
+
3
+ ## Expected Behavior
4
+ <!--- If you're describing a bug, tell us what should happen -->
5
+ <!--- If you're suggesting a change/improvement, tell us how it should work -->
6
+
7
+ ## Current Behavior
8
+ <!--- If describing a bug, tell us what happens instead of the expected behavior -->
9
+ <!--- If suggesting a change/improvement, explain the difference from current behavior -->
10
+
11
+ ## Possible Solution
12
+ <!--- Not obligatory, but suggest a fix/reason for the bug, -->
13
+ <!--- or ideas how to implement the addition or change -->
14
+
15
+ ## Steps to Reproduce (for bugs)
16
+ <!--- Provide a link to a live example, or an unambiguous set of steps to -->
17
+ <!--- reproduce this bug. Include code to reproduce, if relevant -->
18
+ 1.
19
+ 2.
20
+ 3.
21
+ 4.
22
+
23
+ ## Context
24
+ <!--- How has this issue affected you? What are you trying to accomplish? -->
25
+ <!--- Providing context helps us come up with a solution that is most useful in the real world -->
26
+
27
+ ## Your Environment
28
+ <!--- Include as many relevant details about the environment you experienced the bug in -->
29
+ * Version used:
30
+ * Environment name and version (e.g. Python 3.6.1):
31
+ * Operating System and version:
@@ -0,0 +1,30 @@
1
+ <!--- Provide a general summary of your changes in the Title above -->
2
+
3
+ ## Description
4
+ <!--- Describe your changes in detail -->
5
+
6
+ ## Motivation and Context
7
+ <!--- Why is this change required? What problem does it solve? -->
8
+ <!--- If it fixes an open issue, please link to the issue here. -->
9
+
10
+ ## How Has This Been Tested?
11
+ <!--- Please describe in detail how you tested your changes. -->
12
+ <!--- Include details of your testing environment, and the tests you ran to -->
13
+ <!--- see how your change affects other areas of the code, etc. -->
14
+
15
+ ## Screenshots (if appropriate):
16
+
17
+ ## Types of changes
18
+ <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
19
+ - [ ] Bug fix (non-breaking change which fixes an issue)
20
+ - [ ] New feature (non-breaking change which adds functionality)
21
+ - [ ] Breaking change (fix or feature that would cause existing functionality to change)
22
+
23
+ ## Checklist:
24
+ <!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
25
+ <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
26
+ - [ ] My code follows the code style of this project.
27
+ - [ ] My change requires a change to the documentation.
28
+ - [ ] I have updated the documentation accordingly.
29
+ - [ ] I have added tests to cover my changes.
30
+ - [ ] All new and existing tests passed.
data/.gitignore CHANGED
@@ -5,7 +5,7 @@
5
5
  /lib/db/assignments2.json
6
6
  .ghedsh
7
7
  script
8
- tags
8
+
9
9
  *.csv
10
10
  *.gem
11
11
  *.rbc
@@ -36,3 +36,14 @@ doc/
36
36
  .Trashes
37
37
  ehthumbs.db
38
38
  Thumbs.db
39
+
40
+ # TODO file
41
+ TODO.txt
42
+
43
+ # Editor directories and files
44
+ .idea
45
+ .vscode
46
+ *.suo
47
+ *.ntvs*
48
+ *.njsproj
49
+ *.sln
data/.rspec ADDED
@@ -0,0 +1,3 @@
1
+ --require spec_helper
2
+ --color
3
+ --format documentation
@@ -0,0 +1,46 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
+
7
+ ## Our Standards
8
+
9
+ Examples of behavior that contributes to creating a positive environment include:
10
+
11
+ * Using welcoming and inclusive language
12
+ * Being respectful of differing viewpoints and experiences
13
+ * Gracefully accepting constructive criticism
14
+ * Focusing on what is best for the community
15
+ * Showing empathy towards other community members
16
+
17
+ Examples of unacceptable behavior by participants include:
18
+
19
+ * The use of sexualized language or imagery and unwelcome sexual attention or advances
20
+ * Trolling, insulting/derogatory comments, and personal or political attacks
21
+ * Public or private harassment
22
+ * Publishing others' private information, such as a physical or electronic address, without explicit permission
23
+ * Other conduct which could reasonably be considered inappropriate in a professional setting
24
+
25
+ ## Our Responsibilities
26
+
27
+ Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28
+
29
+ Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30
+
31
+ ## Scope
32
+
33
+ This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34
+
35
+ ## Enforcement
36
+
37
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at alu0100816167@ull.edu.es. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
+
39
+ Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40
+
41
+ ## Attribution
42
+
43
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44
+
45
+ [homepage]: http://contributor-covenant.org
46
+ [version]: http://contributor-covenant.org/version/1/4/
data/Gemfile CHANGED
@@ -1,3 +1,8 @@
1
1
  source 'https://rubygems.org'
2
2
 
3
3
  gemspec
4
+
5
+ gem 'tty-prompt'
6
+ gem 'tty-spinner'
7
+ gem 'rainbow'
8
+ gem 'terminal-table'
data/LICENSE ADDED
@@ -0,0 +1,165 @@
1
+ GNU LESSER GENERAL PUBLIC LICENSE
2
+ Version 3, 29 June 2007
3
+
4
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
5
+ Everyone is permitted to copy and distribute verbatim copies
6
+ of this license document, but changing it is not allowed.
7
+
8
+
9
+ This version of the GNU Lesser General Public License incorporates
10
+ the terms and conditions of version 3 of the GNU General Public
11
+ License, supplemented by the additional permissions listed below.
12
+
13
+ 0. Additional Definitions.
14
+
15
+ As used herein, "this License" refers to version 3 of the GNU Lesser
16
+ General Public License, and the "GNU GPL" refers to version 3 of the GNU
17
+ General Public License.
18
+
19
+ "The Library" refers to a covered work governed by this License,
20
+ other than an Application or a Combined Work as defined below.
21
+
22
+ An "Application" is any work that makes use of an interface provided
23
+ by the Library, but which is not otherwise based on the Library.
24
+ Defining a subclass of a class defined by the Library is deemed a mode
25
+ of using an interface provided by the Library.
26
+
27
+ A "Combined Work" is a work produced by combining or linking an
28
+ Application with the Library. The particular version of the Library
29
+ with which the Combined Work was made is also called the "Linked
30
+ Version".
31
+
32
+ The "Minimal Corresponding Source" for a Combined Work means the
33
+ Corresponding Source for the Combined Work, excluding any source code
34
+ for portions of the Combined Work that, considered in isolation, are
35
+ based on the Application, and not on the Linked Version.
36
+
37
+ The "Corresponding Application Code" for a Combined Work means the
38
+ object code and/or source code for the Application, including any data
39
+ and utility programs needed for reproducing the Combined Work from the
40
+ Application, but excluding the System Libraries of the Combined Work.
41
+
42
+ 1. Exception to Section 3 of the GNU GPL.
43
+
44
+ You may convey a covered work under sections 3 and 4 of this License
45
+ without being bound by section 3 of the GNU GPL.
46
+
47
+ 2. Conveying Modified Versions.
48
+
49
+ If you modify a copy of the Library, and, in your modifications, a
50
+ facility refers to a function or data to be supplied by an Application
51
+ that uses the facility (other than as an argument passed when the
52
+ facility is invoked), then you may convey a copy of the modified
53
+ version:
54
+
55
+ a) under this License, provided that you make a good faith effort to
56
+ ensure that, in the event an Application does not supply the
57
+ function or data, the facility still operates, and performs
58
+ whatever part of its purpose remains meaningful, or
59
+
60
+ b) under the GNU GPL, with none of the additional permissions of
61
+ this License applicable to that copy.
62
+
63
+ 3. Object Code Incorporating Material from Library Header Files.
64
+
65
+ The object code form of an Application may incorporate material from
66
+ a header file that is part of the Library. You may convey such object
67
+ code under terms of your choice, provided that, if the incorporated
68
+ material is not limited to numerical parameters, data structure
69
+ layouts and accessors, or small macros, inline functions and templates
70
+ (ten or fewer lines in length), you do both of the following:
71
+
72
+ a) Give prominent notice with each copy of the object code that the
73
+ Library is used in it and that the Library and its use are
74
+ covered by this License.
75
+
76
+ b) Accompany the object code with a copy of the GNU GPL and this license
77
+ document.
78
+
79
+ 4. Combined Works.
80
+
81
+ You may convey a Combined Work under terms of your choice that,
82
+ taken together, effectively do not restrict modification of the
83
+ portions of the Library contained in the Combined Work and reverse
84
+ engineering for debugging such modifications, if you also do each of
85
+ the following:
86
+
87
+ a) Give prominent notice with each copy of the Combined Work that
88
+ the Library is used in it and that the Library and its use are
89
+ covered by this License.
90
+
91
+ b) Accompany the Combined Work with a copy of the GNU GPL and this license
92
+ document.
93
+
94
+ c) For a Combined Work that displays copyright notices during
95
+ execution, include the copyright notice for the Library among
96
+ these notices, as well as a reference directing the user to the
97
+ copies of the GNU GPL and this license document.
98
+
99
+ d) Do one of the following:
100
+
101
+ 0) Convey the Minimal Corresponding Source under the terms of this
102
+ License, and the Corresponding Application Code in a form
103
+ suitable for, and under terms that permit, the user to
104
+ recombine or relink the Application with a modified version of
105
+ the Linked Version to produce a modified Combined Work, in the
106
+ manner specified by section 6 of the GNU GPL for conveying
107
+ Corresponding Source.
108
+
109
+ 1) Use a suitable shared library mechanism for linking with the
110
+ Library. A suitable mechanism is one that (a) uses at run time
111
+ a copy of the Library already present on the user's computer
112
+ system, and (b) will operate properly with a modified version
113
+ of the Library that is interface-compatible with the Linked
114
+ Version.
115
+
116
+ e) Provide Installation Information, but only if you would otherwise
117
+ be required to provide such information under section 6 of the
118
+ GNU GPL, and only to the extent that such information is
119
+ necessary to install and execute a modified version of the
120
+ Combined Work produced by recombining or relinking the
121
+ Application with a modified version of the Linked Version. (If
122
+ you use option 4d0, the Installation Information must accompany
123
+ the Minimal Corresponding Source and Corresponding Application
124
+ Code. If you use option 4d1, you must provide the Installation
125
+ Information in the manner specified by section 6 of the GNU GPL
126
+ for conveying Corresponding Source.)
127
+
128
+ 5. Combined Libraries.
129
+
130
+ You may place library facilities that are a work based on the
131
+ Library side by side in a single library together with other library
132
+ facilities that are not Applications and are not covered by this
133
+ License, and convey such a combined library under terms of your
134
+ choice, if you do both of the following:
135
+
136
+ a) Accompany the combined library with a copy of the same work based
137
+ on the Library, uncombined with any other library facilities,
138
+ conveyed under the terms of this License.
139
+
140
+ b) Give prominent notice with the combined library that part of it
141
+ is a work based on the Library, and explaining where to find the
142
+ accompanying uncombined form of the same work.
143
+
144
+ 6. Revised Versions of the GNU Lesser General Public License.
145
+
146
+ The Free Software Foundation may publish revised and/or new versions
147
+ of the GNU Lesser General Public License from time to time. Such new
148
+ versions will be similar in spirit to the present version, but may
149
+ differ in detail to address new problems or concerns.
150
+
151
+ Each version is given a distinguishing version number. If the
152
+ Library as you received it specifies that a certain numbered version
153
+ of the GNU Lesser General Public License "or any later version"
154
+ applies to it, you have the option of following the terms and
155
+ conditions either of that published version or of any later version
156
+ published by the Free Software Foundation. If the Library as you
157
+ received it does not specify a version number of the GNU Lesser
158
+ General Public License, you may choose any version of the GNU Lesser
159
+ General Public License ever published by the Free Software Foundation.
160
+
161
+ If the Library as you received it specifies that a proxy can decide
162
+ whether future versions of the GNU Lesser General Public License shall
163
+ apply, that proxy's public statement of acceptance of any version is
164
+ permanent authorization for you to choose that version for the
165
+ Library.
data/README.md CHANGED
@@ -1,19 +1,20 @@
1
- ![](http://i125.photobucket.com/albums/p79/NooK1e_RG/ghedsh2_zpsdsdlzg1t.png)
2
1
  # GITHUB EDUCATION SHELL
3
2
 
3
+ ![Gem version badge](https://img.shields.io/badge/version-2.3.8-blue.svg)
4
+
4
5
  A command line program following the philosophy of GitHub Education.
5
6
 
6
7
  ## How does it work?
7
8
 
8
9
  This program give you an interaction with Github like you was using your command line simulating a tree structure. Each level on the tree gives you several options of managing your Github account or your Organization.
9
10
 
10
- Following the philosophy of Github Education, you can use this application to managing your own organization as a classroom where you can make assignments to your students using repository strategies.
11
+ Following the philosophy of Github Education, you can use this application to managing your own organization as a classroom where you can make assignments to your students using repository strategies.
11
12
 
12
13
  ## Installing GHEDSH
13
14
 
14
15
  You can download the gem **ghdesh** from rubygem.
15
16
 
16
- ``gem install ghdesh``
17
+ ``gem install ghedsh``
17
18
 
18
19
  To run the app you need to call the binary file "ghedsh" in your command line after install it. Configuration files are being set in a hidden directory called *.ghedsh*, in your Home path.
19
20
 
@@ -163,47 +164,6 @@ people info <usuario>
163
164
  ```
164
165
  Muestra la informacion extendida de un miembro especifico de una organizacion.
165
166
 
166
- ```
167
- user>organization> new relation file.csv
168
- ```
169
- Esta orden provee un mecanismo para ampliar posteriormente
170
- la información sobre la gente/estudiantes (`people`) en la organización.
171
- Establece una `relación` entre el nombre de usuario GitHub y un campo que servirá para la identificación
172
- del usuario en la institución educativa.
173
-
174
- En este ejemplo se establece el enlace entre la clave primaria de github (el nombre de usuario github)
175
- y el email del alumno/profesor en la universidad:
176
-
177
- ```
178
- crguezl>ULL-ESIT-GRADOII-TFG> new relation tfg-people.csv
179
- ```
180
- El fichero `tfg-people.csv` contiene lo siguiente:
181
- ```
182
- ~/ghedsh(master)]$ cat tfg-people.csv
183
- "github","mail"
184
- "alu0100505023","Clemente.ull.edu.es"
185
- "alu0100769579","Raul.ull.edu.es"
186
- "alu0100816167","Carlos.ull.edu.es"
187
- "berkanrhdz","Berkan.ull.edu.es"
188
- "Cicko","Rudolf.ull.edu.es"
189
- "crguezl","Casiano.ull.edu.es"
190
- "EleDiaz","Eleazar.ull.edu.es"
191
- "jjlabrador","JJ.ull.edu.es"
192
- "Losnen","Samuel.ull.edu.es"
193
- "sokartema","Jazer.ull.edu.es"
194
- ```
195
- Ahora podemos consultar de nuevo la información sobre los miembros:
196
- ```
197
- crguezl>ULL-ESIT-GRADOII-TFG> people info /alu/
198
-
199
- alu0100505023
200
- Github: alu0100505023
201
- Email: Clemente.ull.edu.es
202
-
203
- ...
204
- ```
205
-
206
-
207
167
  ```sh
208
168
  new people info <file>
209
169
  ```
@@ -211,61 +171,14 @@ Añade informacion extendida de los miembros de una organizacion mediante un arc
211
171
 
212
172
  Formato y campos de la informacion añadida: La primera linea del archivo .csv debera indicar el nombre de los campos que seran recogidos por el sistema.
213
173
 
214
- ```
215
- "github", "id", "nombre", "apellido", "emails", "organizaciones", "urls"
216
- ```
174
+ > "github", "id", "nombre", "apellido", "emails", "organizaciones", "urls"
217
175
 
218
176
  Ejemplo del contenido del archivo .csv. A partir de la primera linea de campos, cada nueva linea representara los datos de un alumno. Poniendo dobles comillas se podra añadir varios valores en un mismo campo.
219
177
 
220
- ```
221
- "studentbeta","alu1342","Pedro,Garcia Perez,""alu1342@ull.edu.es, pedrogarciaperez@gmail.com"",""classroom-testing, SYTW1617"",""http://campusvirtual.ull.es/aluXXX, http://pegarpe.github.io""
222
- ```
178
+ > "studentbeta","alu1342","Pedro,Garcia Perez,""alu1342@ull.edu.es, pedrogarciaperez@gmail.com"",""classroom-testing, SYTW1617"",""http://campusvirtual.ull.es/aluXXX, http://pegarpe.github.io""
223
179
 
224
180
  > "studentalpha1","alu321","Paco","Gutierrez","alu321@ull.edu.es","classroom-testing",","http://st.github.com"
225
181
 
226
- Ejemplo:
227
-
228
- ```
229
- crguezl>ULL-ESIT-GRADOII-TFG> new people info tfg-people-2
230
-
231
- Fields found:
232
- "github"
233
- "mail"
234
- "nota"
235
- ```
236
- El fichero `tfg-people-2.csv` contiene:
237
- ```
238
- [~/TFGsrc/clementeTFG/ghedsh(master)]$ cat tfg-people-2.csv
239
- "github","mail","nota"
240
- "alu0100505023","Clemente.ull.edu.es",4
241
- "alu0100769579","Raul.ull.edu.es",6
242
- "alu0100816167","Carlos.ull.edu.es",7
243
- "berkanrhdz","Berkan.ull.edu.es",9
244
- "Cicko","Rudolf.ull.edu.es",8
245
- "crguezl","Casiano.ull.edu.es",5
246
- "EleDiaz","Eleazar.ull.edu.es",6
247
- "jjlabrador","JJ.ull.edu.es",9
248
- "Losnen","Samuel.ull.edu.es",8
249
- "sokartema","Jazer.ull.edu.es",9
250
- ```
251
- Ahora podemos consultar la información añadida:
252
- ```
253
- crguezl>ULL-ESIT-GRADOII-TFG> people info /alu.*6/
254
-
255
- alu0100769579
256
- Github: alu0100769579
257
- Email: Raul.ull.edu.es
258
- Nota: 6
259
-
260
-
261
- alu0100816167
262
- Github: alu0100816167
263
- Email: Carlos.ull.edu.es
264
- Nota: 7
265
- ```
266
-
267
-
268
-
269
182
 
270
183
  ```sh
271
184
  files <path>
data/Rakefile CHANGED
@@ -1,15 +1,9 @@
1
1
  require 'bundler/gem_tasks'
2
- #require 'rspec/core/rake_task'
2
+ require 'rspec/core/rake_task'
3
3
 
4
- #RSpec::Core::RakeTask.new(:spec)
5
-
6
- task default: :bash
7
-
8
- desc "Run simple interace"
9
- task :bash do
10
- sh "ruby bin/ghedsh"
11
- end
4
+ RSpec::Core::RakeTask.new(:test)
12
5
 
6
+ task default: :test
13
7
 
14
8
  desc "publish gem"
15
9
  task :publish do
data/bin/ghedsh CHANGED
@@ -1,4 +1,5 @@
1
1
  #!/usr/bin/env ruby -Ilib
2
2
  require 'interface'
3
3
 
4
- Interface.new
4
+ console = Interface.new
5
+ console.start
@@ -0,0 +1,12 @@
1
+ {
2
+ "members": [{
3
+ "id": "GitHubId1"
4
+ },
5
+ {
6
+ "id": "GitHubId2"
7
+ },
8
+ {
9
+ "id": "GitHubId2"
10
+ }
11
+ ]
12
+ }
@@ -0,0 +1,19 @@
1
+ {
2
+ "teams": [{
3
+ "name": "team_1",
4
+ "members": ["member_1", "member_2", "member_3", "mimebro_4"],
5
+ "privacy": "secret|closed"
6
+ },
7
+
8
+ {
9
+ "name": "team_2",
10
+ "members": ["member_1", "member_2", "member_3", "member_4", "member_5"],
11
+ "privacy": "secret|closed"
12
+ },
13
+ {
14
+ "name": "equipo_3",
15
+ "members": ["member_1", "member_2", "member_3", "member_4", "member_5", "member_6"],
16
+ "privacy": "secret|closed"
17
+ }
18
+ ]
19
+ }
@@ -0,0 +1,12 @@
1
+ {
2
+ "collabs": [{
3
+ "id": "GitHubId1"
4
+ },
5
+ {
6
+ "id": "GitHubId2"
7
+ },
8
+ {
9
+ "id": "GitHubId2"
10
+ }
11
+ ]
12
+ }
@@ -0,0 +1,12 @@
1
+ {
2
+ "remove": [{
3
+ "id": "GitHubId1"
4
+ },
5
+ {
6
+ "id": "GitHubId2"
7
+ },
8
+ {
9
+ "id": "GitHubId2"
10
+ }
11
+ ]
12
+ }
data/ghedsh.gemspec CHANGED
@@ -13,9 +13,10 @@ Gem::Specification.new do |s|
13
13
  s.test_files = s.files.grep(%r{^(test|spec|features)/})
14
14
  s.homepage = 'https://github.com/ULL-ESIT-GRADOII-TFG/ghedsh'
15
15
  s.require_paths = ['lib']
16
- s.required_ruby_version = '>= 1.9.3'
17
- s.add_dependency 'octokit', '~> 3.3'
16
+ s.required_ruby_version = '>= 2.4.0'
17
+ s.add_dependency 'octokit', '~> 4.8'
18
18
  s.add_dependency 'require_all', '~> 1.3.2'
19
19
  s.add_development_dependency 'rake'
20
+ s.add_development_dependency 'rspec', '~> 3.7'
20
21
  s.add_development_dependency 'bundler', '~> 1.5'
21
22
  end