Giter Site home page Giter Site logo

ti-community-infra / tichi Goto Github PK

View Code? Open in Web Editor NEW
45.0 45.0 27.0 4.29 MB

TiChi ☯️ contains the tidb community collaboration automation basic framework and tool set.

Home Page: https://prow.tidb.net

License: Apache License 2.0

Makefile 0.43% Go 97.70% Shell 0.62% Dockerfile 0.27% Rust 0.35% TypeScript 0.55% JavaScript 0.01% SCSS 0.02% CSS 0.04%
cd ci k8s k8s-cluster prow test-infra ti-chi

tichi's People

Contributors

634750802 avatar andylokandy avatar dependabot-preview[bot] avatar dependabot[bot] avatar ekexium avatar mini256 avatar psiace avatar renovate[bot] avatar rustin170506 avatar ti-chi-bot avatar tisonkun avatar wayjam avatar wuhuizuo avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar

Forkers

rustin170506 ti-chi-bot sheetalsingala fireairforce rustin-bot andylokandy yangkeao ziyi-yan zhangysh1995 isgasho mini256 crazycs520 hi-ernest wayjam ekexium 634750802 jingliu2021 tisonkun cadmusjiang lichunzhu longfangsong bot-sandbox mashenjun wuhuizuo jebter rleungx velocitylight

tichi's Issues

Support weighted assignment of reviewers based on code changes

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

Describe the feature you'd like:

Support weighted assignment of reviewers based on code changes

Do you have any ideas on how to implement it?(Optional)

Cleanup the prow doc link

Bug Report

  • I have searched the issues of this repository and believe that this is not a duplicate.

Related link

None

Steps to reproduce(Optional)

What is expected?

Cleanup the prow doc link

What is actually happening?

Create a label-blocker plugin to prevent the manual addition of certain key labels

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

  • Which project: TKV

Describe the feature you'd like:

Create a label-blocker plugin to prevent the manual addition of certain key labels.

For example:
We do not want collaborators to manually add status/can-merge label.

Do you have any ideas on how to implement it?(Optional)

LGTM is triggered multiple times by the same person

Bug Report

  • I have searched the issues of this repository and believe that this is not a duplicate.

Related link

None

Steps to reproduce(Optional)

LGTM multiple times.

What is expected?

Only triggered once.

What is actually happening?

Triggered multiple times.

Standardize each plugin help provider

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None

Describe the feature you'd like:

We need to standardize the help provider for each plugin to provide the standard format and content specification.

Do you have any ideas on how to implement it?(Optional)

Migrate the external plugin config path

Bug Report

  • I have searched the issues of this repository and believe that this is not a duplicate.

Related link

None

Steps to reproduce(Optional)

None

What is expected?

Migrate the external plugin config path.

What is actually happening?

Still in plugins path.

When we use prow bot, we still need to merge the master branch into PR

Bug Report

  • I have searched the issues of this repository and believe that this is not a duplicate.

Related link

None

Steps to reproduce(Optional)

Send a PR, when the master branch update, we need to update it to the PR.

What is expected?

We can automaticly update the out of date PR.

What is actually happening?

We need to update manually.

Need some method to ignore checks for specific PR

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

Describe the feature you'd like:

We got the CI queue boomed when some config samples been edited multiple times today, so we introduced on.<push | pull_request>.ignore-paths option for CI workflows to reduce CI jobs when there're only docs changed in pingcap/tiup#1192

Now if a PR does not change any code most of the CI jobs will not be triggered. But that then lead to a problem that those "required" checks are never going to be satisfied, and then the PR can not be merged in normal way.

Do you have any ideas on how to implement it?(Optional)

We would like to have an command (or by adding a label) to tell bot to ignore checks for some certain PR.

The autoresponder should support all comment events

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None

Describe the feature you'd like:

The autoresponder should support all comment events.

For now it's only support issue comment event.

Do you have any ideas on how to implement it?(Optional)

Support multiple trusted teams for ti-community-owners

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None

Describe the feature you'd like:

Support multiple trusted teams for ti-community-owners.

Do you have any ideas on how to implement it?(Optional)

Add a delay time for blunderbuss to wait for sig label to be added.

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None

Describe the feature you'd like:

Add a delay time for blunderbuss to wait for sig label to be added.

Do you have any ideas on how to implement it?(Optional)

Can I merge my own PR?

Bug Report

  • I have searched the issues of this repository and believe that this is not a duplicate.

In the past we used loose lgtm management, but to ensure that all code is reviewed when merging, the new bot places some restrictions on committers merging their own pr. Submitters are not allowed to merge their own pr directly.

When adding or updating sig label, blunderbuss supports re-cc to reviewers

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None

Describe the feature you'd like:

When adding or updating sig label, blunderbuss supports re-cc to reviewers.

Do you have any ideas on how to implement it?(Optional)

Migrate the test CI to prow jobs

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None

Describe the feature you'd like:

In order to make better use of tide's feature, I want to migrate all the test-related CI of this org to prow job.

Do you have any ideas on how to implement it?(Optional)

Move label and label prefix constants to label.go

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None

Describe the feature you'd like:

Move label and label prefix constants to label.go

Do you have any ideas on how to implement it?(Optional)

Support setting required LGTM numbers for different branches

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

  • Which project:
    tidb-operator
  • PR or Issue Link:

Describe the feature you'd like:

For master branch, we require two LGTMs for each PR.
For release branches, we can require 1 LGTM for each PR.

Do you have any ideas on how to implement it?(Optional)

Make a great name

Feature Request

IMO, ti-community-prow-bot is too long to remember and recall. We may want a new bright and sharp name for it.

Also, we have ti-challenge-bot and ti-community-bot. I'd like to make them into one from the contributors' perspective.

Clean up the events that each plugin responds to

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None

Describe the feature you'd like:

We don't have a clear definition of what each plugin responds to, for example the label plugin should respond to all comment events, not just issue comments, so I think we should clean up all the events and configurations that the plugin responds to.

Do you have any ideas on how to implement it?(Optional)

Support custom lgtm number for owner plugin

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

None

Describe the feature you'd like:

I want to custom the needs lgtm number by PR label.

Do you have any ideas on how to implement it?(Optional)

Support it by owners.

Update branch merging will cover up the /run-all-tests command

Bug Report

  • I have searched the issues of this repository and believe that this is not a duplicate.

Related link

Steps to reproduce(Optional)

/merge a PR that is out of date with the upstream branch.

What is expected?

The bot will update the branch by merging it with the upstream branch and then trigger the /run-all-tests command to run all the integration tests.

What is actually happening?

However, because the merging will also trigger the building and unit tests. It will cover up the integration tests triggered by the /run-all-tests command.

Use JSON Schema to make IDE support yaml lint and hint.

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Describe the feature you'd like:

We can use JSON Schema to make IDE support yaml lint and hint, which can help us avoid some errors on IDE prompts.

Do you have any ideas on how to implement it?(Optional)

We can use jsonschema to automatically generate JSON Schema according to the Go language type definition, and then import the json file into the configuration in the IDE (Such as Goland).

config

type Configuration struct {
	TichiWebURL     string `json:"tichi_web_url,omitempty" jsonschema:"required"`
	PRProcessLink   string `json:"pr_process_link,omitempty" jsonschema:"required"`
	CommandHelpLink string `json:"command_help_link,omitempty" jsonschema:"required"`
}

json generated

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "required": [
    "tichi_web_url",
    "pr_process_link",
    "command_help_link"
  ],
  "properties": {
    "tichi_web_url": {
      "type": "string"
    },
    "pr_process_link": {
      "type": "string"
    },
    "command_help_link": {
      "type": "string"
    },
  },
  "additionalProperties": false,
  "type": "object",
  "definitions": {}
}

preview

image

image

make prow misses github_token.yaml

Bug Report

  • I have searched the issues of this repository and believe that this is not a duplicate.

Related link

  • Which project:

  • PR or Issue Link:

Steps to reproduce(Optional)

cd configs/prow-dev
make prow

What is expected?

It should apply the configuration to the cluster without errors

What is actually happening?

zhangys@xxx:~/utility/ti-community-prow/configs/prow-dev$ make prow
kubectl apply -f cluster/prow_namespace.yaml
namespace/prow unchanged
kubectl apply -f cluster/test-pods_namespace.yaml
namespace/prow-test-pods unchanged
kubectl apply -f cluster/github-token.yaml
error: the path "cluster/github-token.yaml" does not exist
Makefile:10: recipe for target 'github' failed
make: *** [github] Error 1

I don't know what to do to fix it. A better explanation is needed.

docs: add plugins and components summary

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

Describe the feature you'd like:

add plugins and components summary.

Do you have any ideas on how to implement it?(Optional)

Add a page for ti-community-owners

Feature Request

  • I have searched the issues of this repository and believe that this is not a duplicate.

Is your feature request related to a Issue or PR(Optional)

pingcap/tidb-operator#3522 (comment)

Describe the feature you'd like:

For now, we directly expose the URL to the collaborators, and we need a page to display these content.

Do you have any ideas on how to implement it?(Optional)

You can refer to https://pingcap.com/developer/sig/tiup/.

And I suggest you use antd's card to display the collaborators.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.