factory_bot_instrumentation 1.0.2 → 1.1.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: df9495f96882f162c18ca1c8467d09c34d8dc40981ed1a7ba541a7d5200867a9
4
- data.tar.gz: 2ae4e05a4dbd3e729d56ffbfeafb2c14aeef6b6a8e825a6b94023bb6fa379823
3
+ metadata.gz: 4893e1b40e7d03da45c7be90714efdae1c41c10fdf03152c20725100a19ed717
4
+ data.tar.gz: cb2481504a13586d664a02f0314684074938c0eb28ad910cf358482f51277301
5
5
  SHA512:
6
- metadata.gz: c598dcbc2cf1cfc4f7e7c6d9a1e0389f7c9583e9208ae008db35cf320ba740232a9038fb6c00b92b06d95ca5483fee5663b88e70b39c6e7371624494d337f21f
7
- data.tar.gz: dd88ab7d48335f79c874005ea50ee76a6878af89cc3ebbb5333ade70059f084654c20ae83a2200d1d6c2730ced8e58859a4358c8934703f19fa2dfe5f29e766b
6
+ metadata.gz: 3ba69df7c7cc56fbe23d9758b69324938d8ef5db9080c0e6f3aa949e87e8f30f301c1382a8a56d423f8fd88c9d4741db6027f7ab95cb0c0a601919df6e417b0c
7
+ data.tar.gz: d95ae1e9a2ba594536c30ead21c161ff088f33b552b16085c1cf821645dbec61f1f14841e69f7af837ebbae5674b8850a5bcab143986068759dbb200d4d47f98
@@ -0,0 +1,47 @@
1
+ name: Release
2
+ run-name: Release ${{ github.event.inputs.VERSION }}
3
+
4
+ on:
5
+ workflow_dispatch:
6
+ inputs:
7
+ VERSION:
8
+ description: The new version to release. (eg. `1.0.0`) Check the
9
+ changelog for the latest version.
10
+
11
+ concurrency:
12
+ group: '${{ github.event.inputs.VERSION }}'
13
+ cancel-in-progress: true
14
+
15
+ jobs:
16
+ docs:
17
+ name: Release the gem
18
+ runs-on: ubuntu-22.04
19
+ timeout-minutes: 5
20
+ steps:
21
+ - uses: actions/checkout@v3
22
+
23
+ - name: Install Ruby 2.5
24
+ uses: ruby/setup-ruby@v1
25
+ with:
26
+ ruby-version: 2.5
27
+ bundler-cache: true
28
+ rubygems: '3.3.26'
29
+
30
+ - name: Prepare the virtual environment
31
+ uses: hausgold/actions/ci@master
32
+ with:
33
+ clone_token: '${{ secrets.CLONE_TOKEN }}'
34
+ settings: '${{ github.repository }}'
35
+ target: ci/gem-test
36
+
37
+ - name: Switch to SSH remotes for the Git repository
38
+ run: git-ssh-remotes
39
+
40
+ - name: Enforce version '${{ github.event.inputs.VERSION }}'
41
+ run: set-gem-version '${{ github.event.inputs.VERSION }}'
42
+
43
+ - name: Prepare the Git release commit
44
+ run: git-release-commit '${{ github.event.inputs.VERSION }}'
45
+
46
+ - name: Push the release Git commit/tag and package to the registry
47
+ run: make release
data/CHANGELOG.md CHANGED
@@ -1,3 +1,11 @@
1
+ ### next
2
+
3
+ * TODO: Replace this bullet point with an actual description of a change.
4
+
5
+ ### 1.1.0
6
+
7
+ * Added support for Gem release automation
8
+
1
9
  ### 1.0.2
2
10
 
3
11
  * When used in combination with the `factory_bot_rails` gem (>= 6.0) we do not
@@ -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, 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
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at development@hausgold.de. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at [http://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: http://contributor-covenant.org
74
+ [version]: http://contributor-covenant.org/version/1/4/
data/README.md CHANGED
@@ -38,7 +38,9 @@ cases.
38
38
  - [Custom scripts](#custom-scripts)
39
39
  - [Custom styles](#custom-styles)
40
40
  - [Development](#development)
41
+ - [Code of Conduct](#code-of-conduct)
41
42
  - [Contributing](#contributing)
43
+ - [Releasing](#releasing)
42
44
 
43
45
  ## Installation
44
46
 
@@ -730,17 +732,28 @@ application. The file could look like this:
730
732
 
731
733
  ## Development
732
734
 
733
- After checking out the repo, run `bin/setup` to install dependencies. Then, run
734
- `bundle exec rake spec` to run the tests. You can also run `bin/console` for an
735
+ After checking out the repo, run `make install` to install dependencies. Then,
736
+ run `make test` to run the tests. You can also run `make shell-irb` for an
735
737
  interactive prompt that will allow you to experiment.
736
738
 
737
- To install this gem onto your local machine, run `bundle exec rake install`. To
738
- release a new version, update the version number in `version.rb`, and then run
739
- `bundle exec rake release`, which will create a git tag for the version, push
740
- git commits and tags, and push the `.gem` file to
741
- [rubygems.org](https://rubygems.org).
739
+ ## Code of Conduct
740
+
741
+ Everyone interacting in the project codebase, issue tracker, chat
742
+ rooms and mailing lists is expected to follow the [code of
743
+ conduct](./CODE_OF_CONDUCT.md).
742
744
 
743
745
  ## Contributing
744
746
 
745
747
  Bug reports and pull requests are welcome on GitHub at
746
- https://github.com/hausgold/factory_bot_instrumentation.
748
+ https://github.com/hausgold/factory_bot_instrumentation. Make sure that every pull request adds
749
+ a bullet point to the [changelog](./CHANGELOG.md) file with a reference to the
750
+ actual pull request.
751
+
752
+ ## Releasing
753
+
754
+ The release process of this Gem is fully automated. You just need to open the
755
+ Github Actions [Release
756
+ Workflow](https://github.com/hausgold/factory_bot_instrumentation/actions/workflows/release.yml)
757
+ and trigger a new run via the **Run workflow** button. Insert the new version
758
+ number (check the [changelog](./CHANGELOG.md) first for the latest release) and
759
+ you're done.
@@ -4,7 +4,7 @@ module FactoryBot
4
4
  # The gem version details.
5
5
  module Instrumentation
6
6
  # The version of the +factory_bot_instrumentation+ gem
7
- VERSION = '1.0.2'
7
+ VERSION = '1.1.0'
8
8
 
9
9
  class << self
10
10
  # Returns the version of gem as a string.
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: factory_bot_instrumentation
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.2
4
+ version: 1.1.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Hermann Mayer
8
- autorequire:
8
+ autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2023-02-15 00:00:00.000000000 Z
11
+ date: 2023-02-24 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: factory_bot
@@ -271,6 +271,7 @@ extra_rdoc_files: []
271
271
  files:
272
272
  - ".editorconfig"
273
273
  - ".github/workflows/documentation.yml"
274
+ - ".github/workflows/release.yml"
274
275
  - ".github/workflows/test.yml"
275
276
  - ".gitignore"
276
277
  - ".rspec"
@@ -279,6 +280,7 @@ files:
279
280
  - ".yardopts"
280
281
  - Appraisals
281
282
  - CHANGELOG.md
283
+ - CODE_OF_CONDUCT.md
282
284
  - Dockerfile
283
285
  - Envfile
284
286
  - Gemfile
@@ -324,7 +326,7 @@ files:
324
326
  - lib/factory_bot/instrumentation/engine.rb
325
327
  - lib/factory_bot/instrumentation/version.rb
326
328
  - lib/factory_bot_instrumentation.rb
327
- homepage:
329
+ homepage:
328
330
  licenses:
329
331
  - MIT
330
332
  metadata:
@@ -333,7 +335,7 @@ metadata:
333
335
  changelog_uri: https://github.com/hausgold/factory_bot_instrumentation/blob/master/CHANGELOG.md
334
336
  bug_tracker_uri: https://github.com/hausgold/factory_bot_instrumentation/issues
335
337
  documentation_uri: https://www.rubydoc.info/gems/factory_bot_instrumentation
336
- post_install_message:
338
+ post_install_message:
337
339
  rdoc_options: []
338
340
  require_paths:
339
341
  - lib
@@ -348,8 +350,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
348
350
  - !ruby/object:Gem::Version
349
351
  version: '0'
350
352
  requirements: []
351
- rubygems_version: 3.3.8
352
- signing_key:
353
+ rubygems_version: 3.3.26
354
+ signing_key:
353
355
  specification_version: 4
354
356
  summary: Allow your testers to generate test data on demand
355
357
  test_files: []