dpl 1.9.6.travis.2795.5 → 1.9.6.travis.2827.6
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.github/CONTRIBUTING.md +7 -0
- data/.github/stale.yml +53 -0
- data/.travis.yml +3 -2
- data/CODE_OF_CONDUCT.md +74 -0
- data/lib/dpl/version.rb +1 -1
- metadata +4 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: c7f18bbcf10eff9c817e3937661223fd8c14446e0670b542b098eae20eda16cd
|
4
|
+
data.tar.gz: 39a414c8392786ab2efa003b35c4d37933421c8e2d276f0b9074b0b00431d9d4
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: b4b1e55370ce9696e7eebfbaca0cbbb142c3f6b0f84da4236808ade80d1d1b34a0ee8a182b417c4864ad044bb86c8937da404ec9bca6612bfb6be7b5f5bbecf5
|
7
|
+
data.tar.gz: 5513bf4420f7db8fedff0db746d3aff7cba6e7313fee2a1bd044b2694ee7411770e8e88a891b85debc4825bb25d3c5ab7ac0dd34898059112660327571aa04b0
|
data/.github/CONTRIBUTING.md
CHANGED
@@ -164,3 +164,10 @@ with https://github.com/travis-ci/dpl/tree/master/.
|
|
164
164
|
|
165
165
|
When opening a PR, be sure to run at least one deployment with the new configuration,
|
166
166
|
and provide a link to the build in the PR.
|
167
|
+
|
168
|
+
## Automatic closure of old issues
|
169
|
+
|
170
|
+
If an issue has been left open and untouched for 90 days or more, we automatically
|
171
|
+
close them. We do this to ensure that new issues are more easily noticeable, and
|
172
|
+
that old issues that have been resolved or are no longer relevant are closed.
|
173
|
+
You can read more about this [here](https://blog.travis-ci.com/2018-03-09-closing-old-issues).
|
data/.github/stale.yml
ADDED
@@ -0,0 +1,53 @@
|
|
1
|
+
# Configuration for probot-stale - https://github.com/probot/stale
|
2
|
+
|
3
|
+
# Number of days of inactivity before an Issue or Pull Request becomes stale
|
4
|
+
daysUntilStale: 80
|
5
|
+
|
6
|
+
# Number of days of inactivity before a stale Issue or Pull Request is closed.
|
7
|
+
# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
|
8
|
+
daysUntilClose: 10
|
9
|
+
|
10
|
+
# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
|
11
|
+
exemptLabels:
|
12
|
+
- WIP
|
13
|
+
- work in progress
|
14
|
+
- important
|
15
|
+
- locked
|
16
|
+
|
17
|
+
# Set to true to ignore issues in a project (defaults to false)
|
18
|
+
exemptProjects: false
|
19
|
+
|
20
|
+
# Set to true to ignore issues in a milestone (defaults to false)
|
21
|
+
exemptMilestones: false
|
22
|
+
|
23
|
+
# Label to use when marking as stale
|
24
|
+
staleLabel: stale
|
25
|
+
|
26
|
+
# Comment to post when marking as stale. Set to `false` to disable
|
27
|
+
#markComment: >
|
28
|
+
|
29
|
+
# Comment to post when removing the stale label.
|
30
|
+
# unmarkComment: >
|
31
|
+
# Your comment here.
|
32
|
+
|
33
|
+
# Comment to post when closing a stale Issue or Pull Request.
|
34
|
+
closeComment: >
|
35
|
+
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues
|
36
|
+
|
37
|
+
# Limit the number of actions per hour, from 1-30. Default is 30
|
38
|
+
limitPerRun: 30
|
39
|
+
|
40
|
+
# Limit to only `issues` or `pulls`
|
41
|
+
only: issues
|
42
|
+
|
43
|
+
# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
|
44
|
+
# pulls:
|
45
|
+
# daysUntilStale: 30
|
46
|
+
# markComment: >
|
47
|
+
# This pull request has been automatically marked as stale because it has not had
|
48
|
+
# recent activity. It will be closed if no further activity occurs. Thank you
|
49
|
+
# for your contributions.
|
50
|
+
|
51
|
+
# issues:
|
52
|
+
# exemptLabels:
|
53
|
+
# - confirmed
|
data/.travis.yml
CHANGED
@@ -3,6 +3,7 @@ rvm:
|
|
3
3
|
- "2.2.9"
|
4
4
|
- "2.3.6"
|
5
5
|
- "2.4"
|
6
|
+
- "2.5.0"
|
6
7
|
- "2.5"
|
7
8
|
|
8
9
|
jobs:
|
@@ -27,6 +28,8 @@ jobs:
|
|
27
28
|
on:
|
28
29
|
repo: travis-ci/dpl
|
29
30
|
if: branch = master AND NOT type IN (pull_request)
|
31
|
+
allow_failures:
|
32
|
+
- rvm: "2.5"
|
30
33
|
|
31
34
|
env:
|
32
35
|
global:
|
@@ -53,5 +56,3 @@ before_script:
|
|
53
56
|
script:
|
54
57
|
- rake
|
55
58
|
|
56
|
-
notifications:
|
57
|
-
webhooks: "http://requestb.in/1guaq7t1"
|
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
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, other beliefs, 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
|
+
* Being constructive and proportionate when criticizing
|
20
|
+
* Gracefully accepting constructive criticism
|
21
|
+
* Focusing on what is best for the community
|
22
|
+
* Showing empathy towards other community members
|
23
|
+
|
24
|
+
Examples of unacceptable behavior by participants include:
|
25
|
+
|
26
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
27
|
+
advances
|
28
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
29
|
+
* Public or private harassment
|
30
|
+
* Publishing others' private information, such as a physical or electronic
|
31
|
+
address, without explicit permission
|
32
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
33
|
+
professional setting
|
34
|
+
|
35
|
+
## Our Responsibilities
|
36
|
+
|
37
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
38
|
+
behavior and are expected to take appropriate and fair corrective action in
|
39
|
+
response to any instances of unacceptable behavior.
|
40
|
+
|
41
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
42
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
43
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
44
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
45
|
+
threatening, offensive, or harmful.
|
46
|
+
|
47
|
+
## Scope
|
48
|
+
|
49
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
50
|
+
when an individual is representing the project or its community. Examples of
|
51
|
+
representing a project or community include using an official project e-mail
|
52
|
+
address, posting via an official social media account, or acting as an appointed
|
53
|
+
representative at an online or offline event. Representation of a project may be
|
54
|
+
further defined and clarified by project maintainers.
|
55
|
+
|
56
|
+
## Enforcement
|
57
|
+
|
58
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
59
|
+
reported by contacting the project team at the following email address: conduct@travis-ci.org. All
|
60
|
+
complaints will be reviewed and investigated and will result in a response that
|
61
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
62
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
63
|
+
Further details of specific enforcement policies may be posted separately.
|
64
|
+
|
65
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
66
|
+
faith may face temporary or permanent repercussions as determined by other
|
67
|
+
members of the project's leadership.
|
68
|
+
|
69
|
+
## Attribution
|
70
|
+
|
71
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
72
|
+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
|
73
|
+
|
74
|
+
[homepage]: https://www.contributor-covenant.org
|
data/lib/dpl/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: dpl
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.9.6.travis.
|
4
|
+
version: 1.9.6.travis.2827.6
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Konstantin Haase
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2018-
|
11
|
+
date: 2018-04-09 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: rspec
|
@@ -145,9 +145,11 @@ extra_rdoc_files: []
|
|
145
145
|
files:
|
146
146
|
- ".coveralls.yml"
|
147
147
|
- ".github/CONTRIBUTING.md"
|
148
|
+
- ".github/stale.yml"
|
148
149
|
- ".gitignore"
|
149
150
|
- ".rspec"
|
150
151
|
- ".travis.yml"
|
152
|
+
- CODE_OF_CONDUCT.md
|
151
153
|
- Gemfile
|
152
154
|
- LICENSE
|
153
155
|
- README.md
|