about_yml 0.0.6 → 0.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CONTRIBUTING.md +72 -2
- data/README.md +13 -0
- data/lib/about_yml/schema.json +9 -1
- data/lib/about_yml/tasks/check_about_yml.rb +20 -0
- data/lib/about_yml/version.rb +1 -1
- metadata +3 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 4b4a9e428300698f728655e188e34849da008f6d
|
|
4
|
+
data.tar.gz: 04b409c43c3e59cce0a990cfe73ec8f55d56d969
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: a506c911cd0eee21f983dfb2b8fadf1df6fd75d6537ca369fa73a3e706eee25f755dc5f90e2d5d7217310dd40fea8d18b402187b701d64897e023fb12c82f728
|
|
7
|
+
data.tar.gz: 8c93f32818ed4e98f0d470a34d404b7732303feab127b7b656b6f36c7e124647a4d9eb7d8c09352df0cffbe59a34d88280f889591827fc95b129d7079db50b09
|
data/CONTRIBUTING.md
CHANGED
|
@@ -1,8 +1,17 @@
|
|
|
1
1
|
## Welcome!
|
|
2
2
|
|
|
3
|
-
We're so glad you're thinking about contributing to an 18F open source project!
|
|
3
|
+
We're so glad you're thinking about contributing to an 18F open source project!
|
|
4
|
+
If you're unsure or afraid of anything, just ask or submit the issue or pull
|
|
5
|
+
request anyways. The worst that can happen is that you'll be politely asked to
|
|
6
|
+
change something. We appreciate any sort of contribution, and don't want a wall
|
|
7
|
+
of rules to get in the way of that.
|
|
4
8
|
|
|
5
|
-
Before contributing, we encourage you to read our CONTRIBUTING policy (you are
|
|
9
|
+
Before contributing, we encourage you to read our CONTRIBUTING policy (you are
|
|
10
|
+
here), our LICENSE, and our README, all of which should be in this repository.
|
|
11
|
+
If you have any questions, or want to read more about our underlying policies,
|
|
12
|
+
you can consult the 18F Open Source Policy GitHub repository at
|
|
13
|
+
https://github.com/18f/open-source-policy, or just shoot us an email/official
|
|
14
|
+
government letterhead note to [18f@gsa.gov](mailto:18f@gsa.gov).
|
|
6
15
|
|
|
7
16
|
## Public domain
|
|
8
17
|
|
|
@@ -13,3 +22,64 @@ the [CC0 1.0 Universal public domain dedication](https://creativecommons.org/pub
|
|
|
13
22
|
All contributions to this project will be released under the CC0
|
|
14
23
|
dedication. By submitting a pull request, you are agreeing to comply
|
|
15
24
|
with this waiver of copyright interest.
|
|
25
|
+
|
|
26
|
+
## Starting work on an issue
|
|
27
|
+
|
|
28
|
+
Issues that are marked with the `ready` label are ripe for the picking! Simply
|
|
29
|
+
assign yourself to the issue to and change its label to `in progress` to
|
|
30
|
+
indicate that you are working on it.
|
|
31
|
+
|
|
32
|
+
If the issue involves writing code or producing some other change that will
|
|
33
|
+
result in a pull request, begin by creating yourself a branch with a short
|
|
34
|
+
descriptive name of the work that includes the issue number at the end, e.g.,
|
|
35
|
+
`document-pr-process-#36`.
|
|
36
|
+
|
|
37
|
+
**Note:** If you are not a part of the 18F Team, please fork the repository
|
|
38
|
+
first and then create a branch for yourself with the same convention.
|
|
39
|
+
|
|
40
|
+
Once your local branch is created, simply push it remotely and this will
|
|
41
|
+
assign the issue to you and move it to be `in progress` automatically.
|
|
42
|
+
|
|
43
|
+
## Submitting a pull request and completing work
|
|
44
|
+
|
|
45
|
+
When you are satisfied with your work and ready to submit it to be completed,
|
|
46
|
+
please submit a pull request for review. If you haven't already, please
|
|
47
|
+
follow the instructions above and create a branch for yourself first. Prior
|
|
48
|
+
to submitting the pull request, please make note of the following:
|
|
49
|
+
|
|
50
|
+
1. Code changes should be accompanied by tests.
|
|
51
|
+
2. Please run the tests (`$ ./go test`) to make sure there are no regressions.
|
|
52
|
+
|
|
53
|
+
Once everything is ready to go, [submit your pull request](https://help.github.com/articles/using-pull-requests/)!
|
|
54
|
+
When creating a pull request please be sure to reference the issue number it
|
|
55
|
+
is associated with, preferably in the title.
|
|
56
|
+
|
|
57
|
+
If you are working in a branch off of the 18F/about_yml repo directly, you can
|
|
58
|
+
reference the issue like this:
|
|
59
|
+
`Closes #36: Short sentence describing the pull request`
|
|
60
|
+
|
|
61
|
+
If you are working in a forked copy of the repo, please reference the issue
|
|
62
|
+
like this:
|
|
63
|
+
`Closes 18F/about_yml#36: Short sentence describing the pull request`
|
|
64
|
+
|
|
65
|
+
In both cases, please include a descriptive summary of the change in the body
|
|
66
|
+
of the pull request as that will help greatly in reviewing the change and
|
|
67
|
+
understanding what should be taking place inside of it.
|
|
68
|
+
|
|
69
|
+
By referencing the issue in the pull request as noted above, this will
|
|
70
|
+
automatically update the issue with a `needs review` label and notify the
|
|
71
|
+
collaborators on the project that something is ready for a review. One of us
|
|
72
|
+
will take a look as soon as we can and initiate the review process, provide
|
|
73
|
+
feedback as necessary, and ultimately merge the change.
|
|
74
|
+
|
|
75
|
+
Once the code is merged, the branch will be deleted and the `in review`
|
|
76
|
+
label will be removed. The issue will be automatically updated again to be
|
|
77
|
+
marked as Done and Closed.
|
|
78
|
+
|
|
79
|
+
## Performing a review of a pull request
|
|
80
|
+
|
|
81
|
+
If you are performing a review of a pull request please add the `in review`
|
|
82
|
+
label to the pull request and be sure keep the `needs review` label
|
|
83
|
+
associated with it. This will help keep our Waffle board up-to-date and
|
|
84
|
+
reflect that the pull request is being actively reviewed. Also, please
|
|
85
|
+
assign yourself so others know who the primary reviewer is.
|
data/README.md
CHANGED
|
@@ -53,6 +53,19 @@ schema. To check your project's `.about.yml` file:
|
|
|
53
53
|
$ about_yml_validate MY-PROJECT/.about.yml
|
|
54
54
|
```
|
|
55
55
|
|
|
56
|
+
Alternatively, you can add the following to your `Rakefile` to tie
|
|
57
|
+
`.about.yml` validation into your build process (this assumes that `Rakefile`
|
|
58
|
+
and `.about.yml` are both in the top-level project directory):
|
|
59
|
+
|
|
60
|
+
```ruby
|
|
61
|
+
# Development-only tasks
|
|
62
|
+
begin
|
|
63
|
+
require 'about_yml/tasks/check_about_yml'
|
|
64
|
+
task test: :run_about_yml_check
|
|
65
|
+
rescue LoadError
|
|
66
|
+
end
|
|
67
|
+
```
|
|
68
|
+
|
|
56
69
|
### `about_yml_scrape`
|
|
57
70
|
|
|
58
71
|
This program checks for an `.about.yml` file in every GitHub repository
|
data/lib/about_yml/schema.json
CHANGED
|
@@ -214,8 +214,16 @@
|
|
|
214
214
|
"text": {
|
|
215
215
|
"type": "string",
|
|
216
216
|
"description": "Anchor text for the link"
|
|
217
|
+
},
|
|
218
|
+
"category": {
|
|
219
|
+
"type": "string",
|
|
220
|
+
"description": "Type of the link",
|
|
221
|
+
"enum": ["api", "process", "related"]
|
|
217
222
|
}
|
|
218
|
-
}
|
|
223
|
+
},
|
|
224
|
+
"required": [
|
|
225
|
+
"url"
|
|
226
|
+
]
|
|
219
227
|
},
|
|
220
228
|
"contact": {
|
|
221
229
|
"type": "object",
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
require 'about_yml'
|
|
2
|
+
require 'safe_yaml'
|
|
3
|
+
|
|
4
|
+
desc 'Check your .about.yml file'
|
|
5
|
+
task :run_about_yml_check do
|
|
6
|
+
project_dir = Rake.original_dir
|
|
7
|
+
about_file = File.join project_dir, '.about.yml'
|
|
8
|
+
unless File.exist? about_file
|
|
9
|
+
$stderr.puts "No .about.yml file found in #{project_dir}"
|
|
10
|
+
exit 1
|
|
11
|
+
end
|
|
12
|
+
|
|
13
|
+
about_data = SafeYAML.load_file about_file, safe: true
|
|
14
|
+
errors = ::AboutYml::AboutFile.validate_single_file about_data
|
|
15
|
+
unless errors.empty?
|
|
16
|
+
$stderr.puts(".about.yml contains the following validation errors:\n " +
|
|
17
|
+
"#{errors.join("\n ")}")
|
|
18
|
+
exit 1
|
|
19
|
+
end
|
|
20
|
+
end
|
data/lib/about_yml/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: about_yml
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.0.
|
|
4
|
+
version: 0.0.7
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Mike Bland
|
|
@@ -9,7 +9,7 @@ authors:
|
|
|
9
9
|
autorequire:
|
|
10
10
|
bindir: bin
|
|
11
11
|
cert_chain: []
|
|
12
|
-
date: 2015-11
|
|
12
|
+
date: 2015-12-11 00:00:00.000000000 Z
|
|
13
13
|
dependencies:
|
|
14
14
|
- !ruby/object:Gem::Dependency
|
|
15
15
|
name: safe_yaml
|
|
@@ -163,6 +163,7 @@ files:
|
|
|
163
163
|
- lib/about_yml/about.rb
|
|
164
164
|
- lib/about_yml/data_faker.rb
|
|
165
165
|
- lib/about_yml/schema.json
|
|
166
|
+
- lib/about_yml/tasks/check_about_yml.rb
|
|
166
167
|
- lib/about_yml/template_generator.rb
|
|
167
168
|
- lib/about_yml/version.rb
|
|
168
169
|
homepage: https://github.com/18F/about_yml
|