hazem-hosny / github-slideshow

A robot powered training repository :robot:
https://lab.github.com/githubtraining/introduction-to-github
MIT License
1 stars 0 forks source link

ZeoBot's Environment Prepared #14

Open zeobot[bot] opened 4 months ago

zeobot[bot] commented 4 months ago

User description

ZeoBot's Environment Prepared.

The file is stored and will be read from the following location:

branch: `main`
path: .zeobot/config.yml

Description


Changes walkthrough

Relevant files
Configuration changes
config.yml
Zeobot Configuration File Creation                                                         

.zeobot/config.yml
  • Added a comprehensive configuration file for Zeobot with default
    values.
  • Configured various features such as auto-assign, autodelete merged
    branches, branch in progress, contributors commits signed, enforce
    branch merge, license checker, and draft release.
  • Set up rules for pull request handling, branch protection, commit
    signing, and release drafting.
  • Defined templates for draft release names, tags, versions, and
    content.
  • +153/-0 
    💡 Usage Guide ### Checking Your Pull Request Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later. ### Talking to CodeAnt AI Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
    @codeant-ai ask: Your question here
    
    This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code. ### Check Your Repository Health To analyze the health of your code repository, visit our dashboard at [app.codeant.ai](https://app.codeant.ai). This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
    zeobot[bot] commented 4 months ago

    I've just created the configuration file

    The 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  #
    ########################

    :pushpin: This is an automatic response based on @hazem-hosny's action :pushpin: To disable the comments from zeobot, type: :point_right:@zeobot disable comments:point_left:

    semanticdiff-com[bot] commented 4 months ago

    Review changes with SemanticDiff.

    performance-testing-bot[bot] commented 4 months ago

    Unable to locate .performanceTestingBot config file

    vizipi[bot] commented 4 months ago

    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

  • 0.00%[.zeobot/config.yml]