ZeoBot's Environment Prepared#1
Conversation
|
.zeobot/config.yml : should be ########################
# Zeobot Config File #
########################
# Configuration Begins #
########################
# zeobot defaults values for the installed repository
zeobot:
# if enabled, zeobot will run for the repo
enabled: true
# zeobot's commands
commands:
# if enabled, zeobot will detect commands from comments
enabled: false
# write down the users with access to restricted commands
listen_to:
users:
# zeobot's features
features:
# if enabled, zeobot will post comments
can_comment: true
# Auto Assign (AA)
# on new pull request created assign people to it
auto_assign:
# if enabled, AA will work for this repository
enabled: true
use_review_groups: false
use_assignee_groups: false
add_reviewers: true
add_assignees: false
number_of_assignees: 0
number_of_reviewers: 0
review_groups:
assignee_groups:
reviewers_to_add:
assignees_to_add:
skip_keywords:
# Autodelete Merged Branches (AMB)
# after successfully merging a pr, the branch will be deleted
autodelete_merged_branches:
# if enabled, BIP will work for this repository
enabled: true
# branches with this name won't be deleted
branches_to_exclude:
# Branch in Progress (BIP)
# pull requests marked with the '@zeobot-bip' label won't be merged
branch_in_progress:
# if enabled, BIP will work for this repository
enabled: true
# Contributors Commits Signed (CCS)
# pr's that contains unsigned commits will not be merged
contributors_commits_signed:
# if enabled, CCS will work for this repository
enabled: true
# who is required to sign commits
require_for:
# if enabled, the organisation members will have to sign their commits
members: false
# Enforce Branch Merge (EBM)
# enable the access only to some people to merge the branch
enforce_branch_merge:
# if enabled, EBM will work for this repository
enabled: true
# branches where to apply the EBM
branches_to_enforce:
# who has the right to write to protected branches
give_access_to:
# License Checker (LC)
-# branches that contains files without license will not be merged
+# branches that contains diff without license will not be merged
license_checker:
# if enabled, LC will work for this repository
enabled: true
# allowed parameters
allowed:
# people/organisations who own the license
copyright_holders:
# licenses that are approved
licenses:
- # files to check
+ # diff to check
to_check:
# with extension
extensions:
- # files to ignore
+ # diff to ignore
to_ignore:
# with path
- files_path:
+ diff_path:
# Draft Release (DR)
# automatically make a draft release
draft_release:
# if enabled, DR will work for this repository
enabled: true
# draft release template
template:
# release name template
name: 'v$RESOLVED_VERSION'
# release tag template
tag: 'v$RESOLVED_VERSION'
# release version template
version: '$MAJOR.$MINOR.$PATCH'
# release body/content template
content: |
## Changes
$CHANGES
# release body/content changes template
change:
# body/content commit template for each row
template: '- $TITLE (#$NUMBER) by @$AUTHORS'
# title escapes
title_escapes: '\<*_&'
# pr's that contains this labels will
labels_to:
# be excluded from DR
exclude:
# be included in the release body
include:
# generate next version based on the labels
version_resolver:
# major - version category
major:
# these labels will influence the next version
labels:
# minor - version category
minor:
# these labels will influence the next version
labels:
# patch - version category
patch:
# these labels will influence the next version
labels:
# default value
default: 'patch'
# release content/body categories
categories:
# sort items in the body/content
sort:
# pull request are sorted
pull_requests:
# by
by: 'merged_at'
# direction
direction: 'descending'
########################
# Configuration Ends #
######################## |
|
Hey! Changelogs info seems to be missing or might be in incorrect format. |
Optic PR CheckLast updated @ 6:37am UTC on April 5, 2021 UTC Hey! Looks like you do not have Optic tracking this API’s specification. Set up Optic, then check-in a spec to use the bot. Read the Optic Docs Powered by Optic. Not seeing changes? |
|
Unable to locate .performanceTestingBot config file |
|
This pull request seems genuine |
|
It looks like we've not been able to train a model on this repo. Check out why at www.solittlecode.com |
|
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
|
.zeobot/config.yml : should be ########################
# Zeobot Config File #
########################
# Configuration Begins #
########################
# zeobot defaults values for the installed repository
zeobot:
# if enabled, zeobot will run for the repo
enabled: true
# zeobot's commands
commands:
# if enabled, zeobot will detect commands from comments
enabled: false
# write down the users with access to restricted commands
listen_to:
users:
# zeobot's features
features:
# if enabled, zeobot will post comments
can_comment: true
# Auto Assign (AA)
# on new pull request created assign people to it
auto_assign:
# if enabled, AA will work for this repository
enabled: true
use_review_groups: false
use_assignee_groups: false
add_reviewers: true
add_assignees: false
number_of_assignees: 0
number_of_reviewers: 0
review_groups:
assignee_groups:
reviewers_to_add:
assignees_to_add:
skip_keywords:
# Autodelete Merged Branches (AMB)
# after successfully merging a pr, the branch will be deleted
autodelete_merged_branches:
# if enabled, BIP will work for this repository
enabled: true
# branches with this name won't be deleted
branches_to_exclude:
# Branch in Progress (BIP)
# pull requests marked with the '@zeobot-bip' label won't be merged
branch_in_progress:
# if enabled, BIP will work for this repository
enabled: true
# Contributors Commits Signed (CCS)
# pr's that contains unsigned commits will not be merged
contributors_commits_signed:
# if enabled, CCS will work for this repository
enabled: true
# who is required to sign commits
require_for:
# if enabled, the organisation members will have to sign their commits
members: false
# Enforce Branch Merge (EBM)
# enable the access only to some people to merge the branch
enforce_branch_merge:
# if enabled, EBM will work for this repository
enabled: true
# branches where to apply the EBM
branches_to_enforce:
# who has the right to write to protected branches
give_access_to:
# License Checker (LC)
-# branches that contains files without license will not be merged
+# branches that contains title, without license will not be merged
license_checker:
# if enabled, LC will work for this repository
enabled: true
# allowed parameters
allowed:
# people/organisations who own the license
copyright_holders:
# licenses that are approved
licenses:
- # files to check
+ # title, to check
to_check:
# with extension
extensions:
- # files to ignore
+ # title, to ignore
to_ignore:
# with path
- files_path:
+ title,_path:
# Draft Release (DR)
# automatically make a draft release
draft_release:
# if enabled, DR will work for this repository
enabled: true
# draft release template
template:
# release name template
name: 'v$RESOLVED_VERSION'
# release tag template
tag: 'v$RESOLVED_VERSION'
# release version template
version: '$MAJOR.$MINOR.$PATCH'
# release body/content template
content: |
## Changes
$CHANGES
# release body/content changes template
change:
# body/content commit template for each row
template: '- $TITLE (#$NUMBER) by @$AUTHORS'
# title escapes
title_escapes: '\<*_&'
# pr's that contains this labels will
labels_to:
# be excluded from DR
exclude:
# be included in the release body
include:
# generate next version based on the labels
version_resolver:
# major - version category
major:
# these labels will influence the next version
labels:
# minor - version category
minor:
# these labels will influence the next version
labels:
# patch - version category
patch:
# these labels will influence the next version
labels:
# default value
default: 'patch'
# release content/body categories
categories:
# sort items in the body/content
sort:
# pull request are sorted
pull_requests:
# by
by: 'merged_at'
# direction
direction: 'descending'
########################
# Configuration Ends #
######################## |
|
There was an issue running the performance test |
1 similar comment
|
There was an issue running the performance test |
|
Pull request analysis by VIZIPI Below you will find who is the most qualified team member to review your code. 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 requestNo files found with a 40% threashold :) Committed file ranks(click to expand)0.00%[.zeobot/config.yml] |
I've just created the configuration fileThe default values are the following:########################
# Zeobot Config File #
########################
# Configuration Begins #
########################
# zeobot defaults values for the installed repository
zeobot:
# if enabled, zeobot will run for the repo
enabled: true
# zeobot's commands
commands:
# if enabled, zeobot will detect commands from comments
enabled: false
# write down the users with access to restricted commands
listen_to:
users:
# zeobot's features
features:
# if enabled, zeobot will post comments
can_comment: true
# Auto Assign (AA)
# on new pull request created assign people to it
auto_assign:
# if enabled, AA will work for this repository
enabled: true
use_review_groups: false
use_assignee_groups: false
add_reviewers: true
add_assignees: false
number_of_assignees: 0
number_of_reviewers: 0
review_groups:
assignee_groups:
reviewers_to_add:
assignees_to_add:
skip_keywords:
# Autodelete Merged Branches (AMB)
# after successfully merging a pr, the branch will be deleted
autodelete_merged_branches:
# if enabled, BIP will work for this repository
enabled: true
# branches with this name won't be deleted
branches_to_exclude:
# Branch in Progress (BIP)
# pull requests marked with the '@zeobot-bip' label won't be merged
branch_in_progress:
# if enabled, BIP will work for this repository
enabled: true
# Contributors Commits Signed (CCS)
# pr's that contains unsigned commits will not be merged
contributors_commits_signed:
# if enabled, CCS will work for this repository
enabled: true
# who is required to sign commits
require_for:
# if enabled, the organisation members will have to sign their commits
members: false
# Enforce Branch Merge (EBM)
# enable the access only to some people to merge the branch
enforce_branch_merge:
# if enabled, EBM will work for this repository
enabled: true
# branches where to apply the EBM
branches_to_enforce:
# who has the right to write to protected branches
give_access_to:
# License Checker (LC)
# branches that contains files without license will not be merged
license_checker:
# if enabled, LC will work for this repository
enabled: true
# allowed parameters
allowed:
# people/organisations who own the license
copyright_holders:
# licenses that are approved
licenses:
# files to check
to_check:
# with extension
extensions:
# files to ignore
to_ignore:
# with path
files_path:
# Draft Release (DR)
# automatically make a draft release
draft_release:
# if enabled, DR will work for this repository
enabled: true
# draft release template
template:
# release name template
name: 'v$RESOLVED_VERSION'
# release tag template
tag: 'v$RESOLVED_VERSION'
# release version template
version: '$MAJOR.$MINOR.$PATCH'
# release body/content template
content: |
## Changes
$CHANGES
# release body/content changes template
change:
# body/content commit template for each row
template: '- $TITLE (#$NUMBER) by @$AUTHORS'
# title escapes
title_escapes: '\<*_&'
# pr's that contains this labels will
labels_to:
# be excluded from DR
exclude:
# be included in the release body
include:
# generate next version based on the labels
version_resolver:
# major - version category
major:
# these labels will influence the next version
labels:
# minor - version category
minor:
# these labels will influence the next version
labels:
# patch - version category
patch:
# these labels will influence the next version
labels:
# default value
default: 'patch'
# release content/body categories
categories:
# sort items in the body/content
sort:
# pull request are sorted
pull_requests:
# by
by: 'merged_at'
# direction
direction: 'descending'
########################
# Configuration Ends #
########################📌 This is an automatic response based on @willoughbyrm's action |
ZeoBot's Environment Prepared.
The file is stored and will be read from the following location:
masterdefault-branch@zeobot was added to this repo by @willoughbyrm