Skip to content

Conversation

@ARMmaster17
Copy link
Owner

Closes #80

@ARMmaster17 ARMmaster17 added the enhancement New feature or request label May 29, 2022
@ARMmaster17 ARMmaster17 added this to the 2.0.0 milestone May 29, 2022
@ARMmaster17 ARMmaster17 self-assigned this May 29, 2022
@github-actions
Copy link

github-actions bot commented May 29, 2022

Unit Test Results

  48 files   - 12    48 suites   - 12   0s ⏱️ ±0s
  62 tests +  1    62 ✔️ +  1  0 💤 ±0  0 ±0 
186 runs   - 58  186 ✔️  - 58  0 💤 ±0  0 ±0 

Results for commit 026e94f. ± Comparison against base commit c1ac018.

♻️ This comment has been updated with latest results.

@qlty-cloud-legacy
Copy link

Code Climate has analyzed commit 026e94f and detected 3 issues on this pull request.

Here's the issue category breakdown:

Category Count
Complexity 1
Style 2

The test coverage on the diff in this pull request is 87.2% (50% is the threshold).

This pull request will bring the total coverage in the repository to 70.5% (3.7% change).

View more on Code Climate.

@ARMmaster17 ARMmaster17 merged commit ec13e3b into main May 29, 2022
@ARMmaster17 ARMmaster17 deleted the 80-create-arbitrary-locks-with-datacontext-in-pipeline-steps branch May 29, 2022 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create arbitrary locks with DataContext in pipeline steps

2 participants