feat(pingcap/tidb-operator): add trigger for branches and tags

[wuhuizuo]

Signed-off-by: wuhuizuo wuhuizuo@126.com

[ti-chi-bot]

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the PR title and description, it seems that the changes are related to adding triggers for branches and tags in the pingcap/tidb-operator repository.

The actual code changes include adding two new files: git-create-tag.yaml and git-push.yaml for the pingcap/tidb-operator repository and updating the kustomization.yaml file to include these new files.

Overall, the changes seem reasonable, but there are a few potential problems:

• There is no explanation in the PR description about why these triggers are being added or what problem they are solving. It may be useful to add this information to the PR description for context.
• In git-create-tag.yaml and git-push.yaml, there are hardcoded values for builder-resources-memory and builder-resources-cpu. These values may not be appropriate for all environments and could cause issues if not adjusted.
• In git-push.yaml, the filter for branches only includes master and any release- branches. Other branches may also need to be included, depending on the project's branching strategy.

To fix these issues, the PR author could:

• Add to the PR description a brief explanation of why these triggers are being added and what problem they are solving.
• In git-create-tag.yaml and git-push.yaml, use variables or parameters to allow the values for builder-resources-memory and builder-resources-cpu to be configured externally.
• In git-push.yaml, update the filter for branches to include all branches that should trigger a build.

[wuhuizuo]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• apps/prod/OWNERS [wuhuizuo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment