gitlab-dangerfiles 3.9.0 → 3.10.0

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: 5759d8762183090115e7cb10b4b2d7244735d3225b53966c8feaf28e9d9eee7e
4
- data.tar.gz: f49d06c663430072bad4c4f05b8bd1f509ca2c1a095bd1e499e3870fbe061fc9
3
+ metadata.gz: ad2ad158af390c0b6b52fdd86927b4dd0a6118b7b2eca3ad60aaa88ac40b840a
4
+ data.tar.gz: 2872e01e85bf7190e2a3fd4cab71868f2e4924234443797e7479a3ab03497120
5
5
  SHA512:
6
- metadata.gz: 3cd96f3ceb33c2a028f62b1f72a16196ee1afa3768f0463783262ce3a4bd1d98d85e9ab905a916c0ad27cf7bfaf2c16608c5d533e07c30b6463807122d711f09
7
- data.tar.gz: 253aa1b4a8a31c2c323ff05fbad3e2f613b932c82a5f1d61505e92966c1bfe7c593d17bae094f6ebd59b5568433d93d83e443b16df7c75d1b257d1015834a405
6
+ metadata.gz: 7dccc5481318999e83be3a9535983ebbf69d731d5394cf66543df0fd77bf7e274d1b012255c9582a503caae5248956aa2441af1b9ad6ffddf6c5bc2bc730013b
7
+ data.tar.gz: 5d217f45be9fb3c68032bbffd9a7eee4eb4cdb4056200c8dabdaf8255aa084a28ff3cd3ac74a5fa2588634607c4a5d23ffc6d58cc709e9343296112b6b3457b3
data/README.md CHANGED
@@ -218,17 +218,32 @@ danger-review:
218
218
  - bundle add gitlab-dangerfiles --version 3.1.0
219
219
  ```
220
220
 
221
- ## Rake tasks
221
+ ## Local Danger Rake task
222
222
 
223
- You can import this gem's Rake tasks by adding the following to your project's `Rakefile`:
223
+ You can run a Danger Rake task locally in a project to detect Danger errors before pushing commits to a remote
224
+ branch.
224
225
 
225
- ```ruby
226
- require 'gitlab-dangerfiles'
226
+ 1. [Install `gitlab-dangerfiles`](#installation) in your project.
227
+ 1. Add the following to your project's `Rakefile`:
228
+
229
+ ```ruby
230
+ require 'gitlab-dangerfiles'
231
+
232
+ Gitlab::Dangerfiles.load_tasks
233
+ ```
234
+
235
+ To run the Danger Rake task in a project that has `master` as the default branch, run:
227
236
 
228
- Gitlab::Dangerfiles.load_tasks
237
+ ```shell
238
+ bundle exec rake danger_local
229
239
  ```
230
240
 
231
- That will add the `danger_local` Rake task that allows to run Danger locally.
241
+ To run the Danger Rake task in a project that doesn't have `master` as the default branch, you must set the
242
+ `DANGER_LOCAL_BASE` environment variable. For example, in a project with `main` as the default branch:
243
+
244
+ ```shell
245
+ DANGER_LOCAL_BASE="origin/main" bundle exec rake danger_local
246
+ ```
232
247
 
233
248
  ## Documentation
234
249
 
@@ -264,6 +279,12 @@ end
264
279
 
265
280
  See an [example](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92580) for more details.
266
281
 
282
+ ## Contributing
283
+
284
+ Bug reports and merge requests are welcome at https://gitlab.com/gitlab-org/gitlab-dangerfiles. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://gitlab.com/gitlab-org/gitlab-dangerfiles/blob/master/CODE_OF_CONDUCT.md).
285
+
286
+ Make sure to include a changelog entry in your commit message and read the [changelog entries section](https://docs.gitlab.com/ee/development/changelog.html).
287
+
267
288
  ## Release
268
289
 
269
290
  [Automated gem release process](https://gitlab.com/gitlab-org/quality/pipeline-common#release-process) is used to release new version of `gitlab-dangerfiles` through [pipelines](https://gitlab.com/gitlab-org/ruby/gems/gitlab-dangerfiles/-/blob/4f33cf30cab84f7e27ca0cb9a7c0da3ecc675c11/.gitlab-ci.yml#L51), and this will:
@@ -272,24 +293,22 @@ See an [example](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92580) fo
272
293
  - Add a release in the `gitlab-dangerfiles` project: https://gitlab.com/gitlab-org/ruby/gems/gitlab-dangerfiles/-/releases
273
294
  - Populate the release log with the API contents. For example: https://gitlab.com/api/v4/projects/19861191/repository/changelog?version=3.4.4
274
295
 
296
+ We follow this release process in a separate merge request from the one that introduced the changes. The release merge request should just contain a version bump.
297
+
275
298
  ### Before release
276
299
 
277
- Make sure to include a changelog entry in your commit message and read the [changelog entries section](https://docs.gitlab.com/ee/development/changelog.html).
300
+ Changes merged since the last release should have had changelog entries (see [Contributing](#contributing)).
278
301
 
279
- If you forget to set the changelog entry in your commit messages, you can also edit the release notes after it's being released.
302
+ If changelog entries are missing, you can also edit the release notes after it's being released.
280
303
 
281
304
  ### Steps to release
282
305
 
283
- Use a `Release` merge request template and create a merge requet to update the version number in `version.rb`, and get the merge request merged by a maintainer.
306
+ Use a `Release` merge request template and create a merge request to update the version number in `version.rb`, and get the merge request merged by a maintainer.
284
307
 
285
308
  This will then be packaged into a gem and pushed to [rubygems.org](https://rubygems.org) by the CI/CD.
286
309
 
287
310
  For example: [Bump version to 3.4.3](https://gitlab.com/gitlab-org/ruby/gems/gitlab-dangerfiles/-/merge_requests/149).
288
311
 
289
- ## Contributing
290
-
291
- Bug reports and merge requests are welcome at https://gitlab.com/gitlab-org/gitlab-dangerfiles. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://gitlab.com/gitlab-org/gitlab-dangerfiles/blob/master/CODE_OF_CONDUCT.md).
292
-
293
312
  ## License
294
313
 
295
314
  The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
@@ -25,7 +25,7 @@ module Danger
25
25
  engineering_productivity: '~"Engineering Productivity" for CI, Danger',
26
26
  tooling: '~"maintenance::workflow" / ~"maintenance::pipelines" for CI, Danger',
27
27
  ci_template: '~"ci::templates"',
28
- product_intelligence: '~"product intelligence"',
28
+ analytics_instrumentation: '~"analytics instrumentation"',
29
29
  import_integrate_be: '~"group::import and integrate" (backend)',
30
30
  import_integrate_fe: '~"group::import and integrate" (frontend)',
31
31
  "Authentication and Authorization": '~"group::authentication and authorization"',
@@ -89,7 +89,7 @@ module Danger
89
89
  # Fetch an already picked backend maintainer, or pick one otherwise
90
90
  spin.maintainer = backend_spin&.maintainer || spin_for_category(project, :backend, timezone_experiment: including_timezone).maintainer
91
91
  end
92
- when :product_intelligence
92
+ when :analytics_instrumentation
93
93
  spin.optional_role = :maintainer
94
94
 
95
95
  if spin.maintainer.nil?
@@ -92,11 +92,11 @@ categories << :database if helper.mr_labels.include?('database')
92
92
  # Ensure to spin for UX reviewer when ~UX is applied (e.g. to review changes to the UI) except when it's from wider community contribution where we want to assign from the corresponding group
93
93
  categories << :ux if helper.mr_labels.include?('UX') && !helper.mr_labels.include?('Community contribution')
94
94
 
95
- # Ensure to spin for Product Intelligence reviewer when ~"product intelligence::review pending" is applied
96
- categories << :product_intelligence if helper.mr_labels.include?("product intelligence::review pending")
95
+ # Ensure to spin for Analytics Instrumentation reviewer when ~"analytics instrumentation::review pending" is applied
96
+ categories << :analytics_instrumentation if helper.mr_labels.include?("analytics instrumentation::review pending")
97
97
 
98
- # Skip Product intelligence reviews for growth experiment MRs
99
- categories.delete(:product_intelligence) if helper.mr_labels.include?("growth experiment")
98
+ # Skip Analytics Instrumentation reviews for growth experiment MRs
99
+ categories.delete(:analytics_instrumentation) if helper.mr_labels.include?("growth experiment")
100
100
 
101
101
  # Remove disabled categories
102
102
  categories.subtract(helper.config.disabled_roulette_categories)
@@ -76,7 +76,7 @@ module Gitlab
76
76
 
77
77
  def has_particular_capability?(teammate)
78
78
  kind == :reviewer &&
79
- teammate.role.match?(/Backend Engineer.+Manage:Integrations/)
79
+ teammate.role.match?(/Backend Engineer.+Manage:Import and Integrate/)
80
80
  end
81
81
  end
82
82
 
@@ -85,7 +85,7 @@ module Gitlab
85
85
 
86
86
  def has_particular_capability?(teammate)
87
87
  kind == :reviewer &&
88
- teammate.role.match?(/Frontend Engineer.+Manage:Integrations/)
88
+ teammate.role.match?(/Frontend Engineer.+Manage:Import and Integrate/)
89
89
  end
90
90
  end
91
91
 
@@ -1,5 +1,5 @@
1
1
  module Gitlab
2
2
  module Dangerfiles
3
- VERSION = "3.9.0"
3
+ VERSION = "3.10.0"
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: gitlab-dangerfiles
3
3
  version: !ruby/object:Gem::Version
4
- version: 3.9.0
4
+ version: 3.10.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - GitLab
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2023-05-02 00:00:00.000000000 Z
11
+ date: 2023-05-08 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rake