circleci-bundle-update-pr 1.11.1 → 1.11.2

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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: '09ff29855b5e486327154293eb7ebff6465f852b6d7ae902723156667f3d54c9'
4
- data.tar.gz: 1d64f35097cd4760ca95009c32cf05be3d5eab9d7209efed4d171e6db21bff8d
3
+ metadata.gz: 27f51bdea4d44838fc9bf9e1440167a424e09d7e844b51db0cd11ff5b1a581e1
4
+ data.tar.gz: a22a1d4620e678087ae5fa2002b2caef6f24e991e2a4d12f2f6e18d30490aadb
5
5
  SHA512:
6
- metadata.gz: 4d8d71870cae7ae77816648338641e9050c9cb2dceb42d911aed094095c3458d0e90e78cdaa6adfce677365980b7a5e087fefc1b48292cc3e27a5660de4154d8
7
- data.tar.gz: 4c39a0f5dd0e6d2bef6afb63cf605d90a3045795a0c219eb4f37178a86673d69964a56a796be35658c9c4f668db1a0a1acab7058c9027ef183bd370942aef97e
6
+ metadata.gz: 1c6978e03200732161eaf5779f2182fa0140ed3338134ac943c9a489d24ce8ad7910257a273f3225b9b9f89a8fa976647b125bcf10504161464516480b966699
7
+ data.tar.gz: 3c5f95b5ec547abcae5f0fee2a83a0db56217c1faace01437bd10c936ab8a3e51d4baa7f27fc16b8683301812f48eca79112705b1b99a77ea844f4b644cc13fb
data/.circleci/config.yml CHANGED
@@ -11,7 +11,6 @@ jobs:
11
11
  # See also https://circleci.com/docs/2.0/custom-images/#adding-required-and-custom-tools-or-files
12
12
  apk add --update --no-cache git openssh-client tar gzip ca-certificates \
13
13
  tzdata
14
- gem install -N bundler
15
14
  - run: &set_timezone
16
15
  name: Set timezone to Asia/Tokyo
17
16
  command: cp /usr/share/zoneinfo/Asia/Tokyo /etc/localtime
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- circleci-bundle-update-pr (1.11.1)
4
+ circleci-bundle-update-pr (1.11.2)
5
5
  compare_linker (>= 1.4.0)
6
6
  octokit
7
7
 
@@ -10,7 +10,7 @@ GEM
10
10
  specs:
11
11
  addressable (2.5.2)
12
12
  public_suffix (>= 2.0.2, < 4.0)
13
- compare_linker (1.4.0)
13
+ compare_linker (1.4.1)
14
14
  httpclient
15
15
  octokit
16
16
  diff-lcs (1.3)
@@ -18,23 +18,23 @@ GEM
18
18
  multipart-post (>= 1.2, < 3)
19
19
  httpclient (2.8.3)
20
20
  multipart-post (2.0.0)
21
- octokit (4.9.0)
21
+ octokit (4.12.0)
22
22
  sawyer (~> 0.8.0, >= 0.5.3)
23
- public_suffix (3.0.2)
23
+ public_suffix (3.0.3)
24
24
  rake (12.3.1)
25
- rspec (3.7.0)
26
- rspec-core (~> 3.7.0)
27
- rspec-expectations (~> 3.7.0)
28
- rspec-mocks (~> 3.7.0)
29
- rspec-core (3.7.1)
30
- rspec-support (~> 3.7.0)
31
- rspec-expectations (3.7.0)
25
+ rspec (3.8.0)
26
+ rspec-core (~> 3.8.0)
27
+ rspec-expectations (~> 3.8.0)
28
+ rspec-mocks (~> 3.8.0)
29
+ rspec-core (3.8.0)
30
+ rspec-support (~> 3.8.0)
31
+ rspec-expectations (3.8.1)
32
32
  diff-lcs (>= 1.2.0, < 2.0)
33
- rspec-support (~> 3.7.0)
34
- rspec-mocks (3.7.0)
33
+ rspec-support (~> 3.8.0)
34
+ rspec-mocks (3.8.0)
35
35
  diff-lcs (>= 1.2.0, < 2.0)
36
- rspec-support (~> 3.7.0)
37
- rspec-support (3.7.1)
36
+ rspec-support (~> 3.8.0)
37
+ rspec-support (3.8.0)
38
38
  sawyer (0.8.1)
39
39
  addressable (>= 2.3.5, < 2.6)
40
40
  faraday (~> 0.8, < 1.0)
@@ -51,4 +51,4 @@ DEPENDENCIES
51
51
  rspec (~> 3.7)
52
52
 
53
53
  BUNDLED WITH
54
- 1.16.2
54
+ 1.16.4
data/README.md CHANGED
@@ -8,12 +8,10 @@
8
8
  [license]: https://github.com/masutaka/circleci-bundle-update-pr/blob/master/LICENSE.txt
9
9
  [gem-link]: http://badge.fury.io/rb/circleci-bundle-update-pr
10
10
 
11
- `circleci-bundle-update-pr` is an automation script for continuous bundle update and for sending a pull request using [`Scheduling a Workflow of CircleCI 2.0`](https://circleci.com/docs/2.0/workflows/#scheduling-a-workflow).
11
+ `circleci-bundle-update-pr` is an automation script for continuous bundle update and for sending a pull request using [`Scheduling a Workflow of CircleCI`](https://circleci.com/docs/2.0/workflows/#scheduling-a-workflow).
12
12
 
13
13
  By requesting a nightly build to CircleCI with an environment variable configured in `circle.yml` or `.circleci/config.yml` to execute this script, bundle update is invoked, then commit changes and send a pull request to GitHub repository if there some changes exist.
14
14
 
15
- :bulb: [README.md for CircleCI 1.0 is here.](README-for-CircleCI-1.0.md)
16
-
17
15
  ## Installation
18
16
 
19
17
  ```
@@ -2,7 +2,7 @@ module Circleci
2
2
  module Bundle
3
3
  module Update
4
4
  module Pr
5
- VERSION = "1.11.1"
5
+ VERSION = "1.11.2"
6
6
  end
7
7
  end
8
8
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: circleci-bundle-update-pr
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.11.1
4
+ version: 1.11.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Takashi Masuda
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2018-07-15 00:00:00.000000000 Z
11
+ date: 2018-09-17 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: octokit
@@ -94,7 +94,6 @@ files:
94
94
  - Gemfile
95
95
  - Gemfile.lock
96
96
  - LICENSE.txt
97
- - README-for-CircleCI-1.0.md
98
97
  - README.md
99
98
  - Rakefile
100
99
  - bin/circleci-bundle-update-pr
@@ -1,121 +0,0 @@
1
- # Circleci::Bundle::Update::Pr
2
-
3
- [![Build Status](https://img.shields.io/circleci/project/masutaka/circleci-bundle-update-pr/master.svg?style=flat-square)][circleci]
4
- [![License](https://img.shields.io/github/license/masutaka/circleci-bundle-update-pr.svg?style=flat-square)][license]
5
- [![Gem](https://img.shields.io/gem/v/circleci-bundle-update-pr.svg?style=flat-square)][gem-link]
6
-
7
- [circleci]: https://circleci.com/gh/masutaka/circleci-bundle-update-pr
8
- [license]: https://github.com/masutaka/circleci-bundle-update-pr/blob/master/LICENSE.txt
9
- [gem-link]: http://badge.fury.io/rb/circleci-bundle-update-pr
10
-
11
- circleci-bundle-update-pr is an automation script for continuous bundle update and for sending a pull request via CircleCI [Nightly builds](https://circleci.com/docs/nightly-builds/).
12
-
13
- By requesting a nightly build to CircleCI with an environment variable configured in `circle.yml` to execute this script, bundle update is invoked, then commit changes and send a pull request to GitHub repository if there some changes exist.
14
-
15
- ## Installation
16
-
17
- ```
18
- $ gem install circleci-bundle-update-pr
19
- ```
20
-
21
- ## Prerequisites
22
-
23
- The application on which you want to run continuous bundle update must be configured to be built on CircleCI.
24
-
25
- ## Usage
26
-
27
- ### Setting GitHub personal access token to CircleCI
28
-
29
- GitHub personal access token is required for sending pull requests to your repository.
30
-
31
- 1. Go to [your account's settings page](https://github.com/settings/tokens) and generate a personal access token with "repo" scope
32
- 2. On CircleCI dashboard, go to your application's "Project Settings" -> "Environment Variables"
33
- 3. Add an environment variable `GITHUB_ACCESS_TOKEN` with your GitHub personal access token
34
- * If use GitHub Enterprise
35
- * `ENTERPRISE_OCTOKIT_ACCESS_TOKEN` with your GitHub Enterprise personal access token
36
- * `ENTERPRISE_OCTOKIT_API_ENDPOINT` with your GitHub Enterprise api endpoint (e.g. https://www.example.com/api/v3)
37
-
38
- ### Getting CircleCI API token
39
-
40
- CircleCI API token is required to trigger nightly builds.
41
-
42
- 1. Go to your application's "Project Settings" -> "API Permissions"
43
- 2. Select "Create Token" and create a new token with "All" scope and any label you like
44
-
45
- ### Configure circle.yml
46
-
47
- Configure your `circle.yml` to run `circleci-bundle-update-pr` if `BUNDLE_UPDATE` environment variable is present, for example:
48
-
49
- ```yaml
50
- deployment:
51
- production:
52
- branch: master
53
- commands:
54
- - |
55
- if [ "${BUNDLE_UPDATE}" ] ; then
56
- gem update bundler -N
57
- gem install circleci-bundle-update-pr -N
58
- circleci-bundle-update-pr <username> <email>
59
- fi
60
- ```
61
-
62
- NOTE: Please make sure you replace `<username>` and `<email>` with yours.
63
-
64
- ### Trigger nightly build API via curl
65
-
66
- The easiest way to start a nightly build is using curl. The below is a simple script to trigger a build.
67
-
68
- ```bash
69
- _project=<username>/<reponame>
70
- _branch=master
71
- _circle_token=<ciecleci api token>
72
-
73
- trigger_build_url=https://circleci.com/api/v1/project/${_project}/tree/${_branch}?circle-token=${_circle_token}
74
-
75
- post_data='{ "build_parameters": { "BUNDLE_UPDATE": "true" } }'
76
-
77
- curl \
78
- --header "Accept: application/json" \
79
- --header "Content-Type: application/json" \
80
- --data "${post_data}" \
81
- --request POST ${trigger_build_url}
82
- ```
83
-
84
- NOTE: Please do not forget to replace `<username>/<reponame>/<circleci api token>` with yours.
85
-
86
-
87
- ### Trigger nightly build via ci-build-trigger (recommended)
88
-
89
- While you can trigger nightly builds by using whatever you want for sending requests to API, the most recommended way is to use "ci-build-trigger". Please see https://github.com/masutaka/ci-build-trigger for details.
90
-
91
- ## CLI command references
92
-
93
- General usage:
94
-
95
- ```
96
- $ circleci-bundle-update-pr <git username> <git email address>
97
- ```
98
-
99
- By default, it works only on master branch, but you can also explicitly specify any branches rather than only master branch by adding them to the arguments.
100
-
101
- ```
102
- $ circleci-bundle-update-pr <git username> <git email address> master develop topic
103
- ```
104
-
105
- You can also add the following options:
106
-
107
- ```
108
- $ circleci-bundle-update-pr -h
109
- Usage: circleci-bundle-update-pr [options]
110
- -a, --assignees alice,bob,carol Assign the PR to them
111
- -r, --reviewers alice,bob,carol Request PR review to them
112
- -l, --labels "In Review, Update" Add labels to the PR
113
- ```
114
-
115
- ## Contributing
116
-
117
- 1. Fork it ( https://github.com/masutaka/circleci-bundle-update-pr/fork )
118
- 2. Create your feature branch (`git checkout -b my-new-feature`)
119
- 3. Commit your changes (`git commit -am 'Add some feature'`)
120
- 4. Push to the branch (`git push origin my-new-feature`)
121
- 5. Create a new Pull Request