Thoth Configuration Initialization by khebhut[bot] · Pull Request #3 · willoughbyrm/docs

khebhut · 2022-01-22T19:04:13Z

Automatic configuration initialization

The Kebechet app was installed on this repository but no configuration was
found. This PR contains basic configuration of runtime environments and
managers.

changelogg · 2022-01-22T19:04:16Z

Hey! Changelogs info seems to be missing or might be in incorrect format.
Please use the below template in PR description to ensure Changelogg can detect your changes:
- (tag) changelog_text
or
- tag: changelog_text
OR
You can add tag in PR header or while doing a commit too
(tag) PR header
or
tag: PR header
Valid tags: added / feat, changed, deprecated, fixed / fix, removed, security, build, ci, chore, docs, perf, refactor, revert, style, test
Thanks!
For more info, check out changelogg docs

performance-testing-bot · 2022-01-22T19:04:17Z

Unable to locate .performanceTestingBot config file

pull-request-quantifier-deprecated · 2022-01-22T19:04:19Z

This PR has 33 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

Label      : Extra Small
Size       : +33 -0
Percentile : 13.2%

Total files changed: 1

Change summary by file extension:
.yaml : +33 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

Fast and predictable releases to production:
- Optimal size changes are more likely to be reviewed faster with fewer
  iterations.
- Similarity in low PR complexity drives similar review times.
Review quality is likely higher as complexity is lower:
- Bugs are more likely to be detected.
- Code inconsistencies are more likely to be detetcted.
Knowledge sharing is improved within the participants:
- Small portions can be assimilated better.
Better engineering practices are exercised:
- Solving big problems by dividing them in well contained, smaller problems.
- Exercising separation of concerns within the code changes.

What can I do to optimize my changes

Use the PullRequestQuantifier to quantify your PR accurately
- Create a context profile for your repo using the context generator
- Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
- Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
- Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
Change your engineering behaviors
- For PRs that fall outside of the desired spectrum, review the details and check if:
  - Your PR could be split in smaller, self-contained PRs instead
  - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

One line was added: +1 -0
One line was deleted: +0 -1
One line was modified: +1 -1 (git diff doesn't know about modified, it will
interpret that line like one addition plus one deletion)
Change percentiles: Change characteristics (addition, deletion, modification)
of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

mergebase-codegreen

Mergebase Code Green

Updated Vulnerability Report

The report below shows the state of the repository after the pull request.

Critical

Vulnerability	Dependency	Source Path
CVE-2019-10744	npm:lodash.defaults:4.2.0	package-lock.json
CVE-2021-26707	npm:merge-deep:3.0.2	package-lock.json

Extra High

Vulnerability	Dependency	Source Path
CVE-2020-8265	npm:@types/node:14.10.0	package-lock.json

High

Vulnerability	Dependency	Source Path
CVE-2021-33502	npm:@sindresorhus/is:0.14.0	package-lock.json
CVE-2021-33502	npm:@sindresorhus/is:2.1.1	package-lock.json
CVE-2021-33502	npm:@szmarczak/http-timer:1.1.2	package-lock.json
CVE-2021-33502	npm:@szmarczak/http-timer:4.0.5	package-lock.json
CVE-2021-33502	npm:@types/cacheable-request:6.0.1	package-lock.json
CVE-2021-33502	npm:@types/http-cache-semantics:4.0.0	package-lock.json
CVE-2021-33502	npm:@types/keyv:3.1.1	package-lock.json
CVE-2021-22884, CVE-2021-22883, CVE-2020-8277, CVE-2020-8252, CVE-2020-8251, CVE-2020-8201	npm:@types/node:14.10.0	package-lock.json
CVE-2021-33502	npm:@types/responselike:1.0.0	package-lock.json
CVE-2021-33502	npm:cacheable-lookup:2.0.1	package-lock.json
CVE-2021-33502	npm:cacheable-request:6.1.0	package-lock.json
CVE-2021-33502	npm:cacheable-request:7.0.1	package-lock.json
CVE-2021-33502	npm:clone-response:1.0.2	package-lock.json
CVE-2021-33502	npm:defer-to-connect:1.1.3	package-lock.json
CVE-2021-33502	npm:defer-to-connect:2.0.0	package-lock.json
CVE-2020-28469	npm:glob-parent:3.1.0	package-lock.json
CVE-2020-28469	npm:glob-parent:5.1.0	package-lock.json
CVE-2020-28469	npm:glob-parent:5.1.1	package-lock.json
CVE-2021-33502	npm:got:10.7.0	package-lock.json
CVE-2021-33502	npm:got:9.6.0	package-lock.json
CVE-2021-33502	npm:http-cache-semantics:4.0.3	package-lock.json
CVE-2021-33502	npm:keyv:3.1.0	package-lock.json
CVE-2021-33502	npm:keyv:4.0.1	package-lock.json
CVE-2019-20149	npm:kind-of:2.0.1	package-lock.json
CVE-2019-20149	npm:kind-of:3.2.2	package-lock.json
CVE-2019-20149	npm:kind-of:4.0.0	package-lock.json
CVE-2019-20149	npm:kind-of:5.1.0	package-lock.json
CVE-2021-23337	npm:lodash.assignin:4.2.0	package-lock.json
CVE-2021-23337	npm:lodash.bind:4.2.1	package-lock.json
CVE-2021-23337	npm:lodash.defaults:4.2.0	package-lock.json
CVE-2021-23337	npm:lodash.filter:4.6.0	package-lock.json
CVE-2021-23337	npm:lodash.flatten:4.4.0	package-lock.json
CVE-2021-23337	npm:lodash.foreach:4.5.0	package-lock.json
CVE-2021-23337	npm:lodash.get:4.4.2	package-lock.json
CVE-2021-23337	npm:lodash.map:4.6.0	package-lock.json
CVE-2021-23337	npm:lodash.merge:4.6.2	package-lock.json
CVE-2021-23337	npm:lodash.pick:4.4.0	package-lock.json
CVE-2021-23337	npm:lodash.reduce:4.6.0	package-lock.json
CVE-2021-23337	npm:lodash.reject:4.6.0	package-lock.json
CVE-2021-23337	npm:lodash.set:4.3.2	package-lock.json
CVE-2021-23337	npm:lodash.some:4.6.0	package-lock.json
CVE-2021-23337	npm:lodash.sortby:4.7.0	package-lock.json
CVE-2021-23337	npm:lodash.uniq:4.5.0	package-lock.json
CVE-2021-23337	npm:lodash:4.17.20	package-lock.json
CVE-2021-21306	npm:marked:1.2.9	package-lock.json
CVE-2021-33502	npm:normalize-url:1.9.1	package-lock.json
CVE-2021-33502	npm:normalize-url:4.2.0	package-lock.json
CVE-2021-29469	npm:redis-commands:1.6.0	package-lock.json
CVE-2021-29469	npm:redis-errors:1.2.0	package-lock.json
CVE-2021-29469	npm:redis-parser:3.0.0	package-lock.json
CVE-2021-29469	npm:redis:3.0.2	package-lock.json
CVE-2021-33502	npm:responselike:1.0.2	package-lock.json
CVE-2021-33502	npm:responselike:2.0.0	package-lock.json
CVE-2021-27290	npm:ssri:6.0.1	package-lock.json
CVE-2021-27290	npm:ssri:8.0.0	package-lock.json
CVE-2018-7408	npm:tar:4.4.13	package-lock.json
CVE-2017-15010	npm:tough-cookie:2.4.3	package-lock.json
CVE-2020-7774	npm:y18n:4.0.0	package-lock.json

Medium

Vulnerability	Dependency	Source Path
CVE-2020-7598	npm:@types/minimist:1.2.1	package-lock.json
CVE-2020-8287	npm:@types/node:14.10.0	package-lock.json
CVE-2020-7608	npm:@types/yargs-parser:13.1.0	package-lock.json
CVE-2020-15366	npm:ajv:6.11.0	package-lock.json
CVE-2020-8244	npm:bl:4.0.3	package-lock.json
CVE-2021-23364	npm:browserslist:4.16.3	package-lock.json
CVE-2021-23382	npm:colorette:1.2.1	package-lock.json
CVE-2020-28498	npm:elliptic:6.5.3	package-lock.json
CVE-2021-23362	npm:hosted-git-info:2.7.1	package-lock.json
CVE-2020-28500	npm:lodash.assignin:4.2.0	package-lock.json
CVE-2020-28500	npm:lodash.bind:4.2.1	package-lock.json
CVE-2020-28500, CVE-2018-3721, CVE-2018-16487	npm:lodash.defaults:4.2.0	package-lock.json
CVE-2020-28500	npm:lodash.filter:4.6.0	package-lock.json
CVE-2020-28500	npm:lodash.flatten:4.4.0	package-lock.json
CVE-2020-28500	npm:lodash.foreach:4.5.0	package-lock.json
CVE-2020-28500	npm:lodash.get:4.4.2	package-lock.json
CVE-2020-28500	npm:lodash.map:4.6.0	package-lock.json
CVE-2020-28500	npm:lodash.merge:4.6.2	package-lock.json
CVE-2020-28500	npm:lodash.pick:4.4.0	package-lock.json
CVE-2020-28500	npm:lodash.reduce:4.6.0	package-lock.json
CVE-2020-28500	npm:lodash.reject:4.6.0	package-lock.json
CVE-2020-28500	npm:lodash.set:4.3.2	package-lock.json
CVE-2020-28500	npm:lodash.some:4.6.0	package-lock.json
CVE-2020-28500	npm:lodash.sortby:4.7.0	package-lock.json
CVE-2020-28500	npm:lodash.uniq:4.5.0	package-lock.json
CVE-2020-28500	npm:lodash:4.17.20	package-lock.json
CVE-2021-23382, CVE-2021-23368	npm:postcss:7.0.21	package-lock.json
CVE-2021-23382, CVE-2021-23368	npm:postcss:7.0.35	package-lock.json
CVE-2018-6341	npm:scheduler:0.20.1	package-lock.json
CVE-2021-32640	npm:ws:6.2.1	package-lock.json
CVE-2021-32640	npm:ws:7.2.5	package-lock.json

Low

Vulnerability	Dependency	Source Path
CVE-2013-7035	npm:react-dom:17.0.1	package-lock.json
CVE-2013-7035	npm:react-is:16.13.1	package-lock.json
CVE-2013-7035	npm:react:17.0.1	package-lock.json
CVE-2013-7035	npm:scheduler:0.20.1	package-lock.json

vizipi · 2022-01-22T19:05:34Z

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code.
This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below ) Feedback always welcome

No other active qualified developers found to review these specific changes. You might consider involving more team members with these code segments.

Potential missing files from this Pull request

No files found with a 40% threashold :)
No commonly committed files found with a 40% threashold

Committed file ranks

(click to expand)

0.00%[.thoth.yaml]

Initialize .thoth.yaml with basic configuration

f720430

pull-request-quantifier-deprecated bot added the Extra Small label Jan 22, 2022

mergebase-codegreen bot approved these changes Jan 22, 2022

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Thoth Configuration Initialization#3

Thoth Configuration Initialization#3
khebhut[bot] wants to merge 1 commit intomainfrom
kebechet-initial-thoth-config

khebhut bot commented Jan 22, 2022

Uh oh!

changelogg bot commented Jan 22, 2022

Uh oh!

performance-testing-bot bot commented Jan 22, 2022

Uh oh!

pull-request-quantifier-deprecated bot commented Jan 22, 2022

What can I do to optimize my changes

How to interpret the change counts in git diff output

Uh oh!

mergebase-codegreen bot left a comment

Uh oh!

vizipi bot commented Jan 22, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

khebhut bot commented Jan 22, 2022

Automatic configuration initialization

Uh oh!

changelogg bot commented Jan 22, 2022

Uh oh!

performance-testing-bot bot commented Jan 22, 2022

Uh oh!

pull-request-quantifier-deprecated bot commented Jan 22, 2022

What can I do to optimize my changes

How to interpret the change counts in git diff output

Uh oh!

mergebase-codegreen bot left a comment

Choose a reason for hiding this comment

Mergebase Code Green

Updated Vulnerability Report

Critical

Extra High

High

Medium

Low

Uh oh!

vizipi bot commented Jan 22, 2022

Potential missing files from this Pull request

Committed file ranks

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants