As we enter the first month of the Year of the Tiger, everyone is back to the normal pace of work. Of course, the Gitee team is not idle, bringing you the first wave of updates for the New Year. Let’s take a look at these super practical new features with Ma Jianchang!

Push rule restrictions

In the research and development management process, the establishment of a certain consensus has become a standard practice in the industry. The benefits of consensus establishment are to reduce communication costs, solidify some behavior patterns of the team, make the team more focused on business development without spending too much energy in the research and development process, and reduce the cognitive load of the team.

Based on the above considerations, Gitee launched the push rule restriction function to help the team make more progress in submission standardization and reduce the cost of manual intervention. Through the configuration of push rule, the team can flexibly configure in line with some hard restrictions of team culture.

The current push rule setting includes the following dimensions:

1. Specify whether you can only push your own submission (the submission email address must be consistent with the registered email address of the push user);

2. Specify the suffix of the email address for submission (for example, only internal email addresses are allowed, such as @gitee.com).

3. Regex validation of submission information (specify the format of submission information, for example, must be fix: #888 bug fixed);

4. Limit the size of a single file (specify the maximum single file size that can be committed, such as 5M).

For more information on push rule restrictions, go to the Gitee Help Center/Update Log.

Dependent packet jump

When using package management tools such as NPM/RPM/YARN, a description file is automatically generated (for example, package.json is generated using NPM). This file describes all information about the package, including author, introduction, package dependencies, build information, and so on.

When learning about open source projects, many developers often visit the description file to view the dependencies of the project. In order to make it easier for developers to directly access these dependencies, Gitee has introduced a small feature that allows developers to go to the dependencies address with a single click.

In the repository’s file browsing page, dependency packages that you can directly click to access are marked in orange to go to the component’s original repository.

CodeOwners

The PR submitted during the daily iteration delivery assigns members of the group to conduct code reviews, and when code changes involve A file or directory A, in most cases A permanent person B is assigned to conduct code reviews. We can say that B is the CodeOwner of component A. Simply put, Codeowner defines who is responsible for a particular file or directory in the repository.

To use the CodeOwners feature, you need to create a file in the repository called CodeOwners to see the rules.

After the setting is completed, after submitting PR, the corresponding person in charge can be automatically assigned to review the modification of a file or directory according to the set rules, without manual setting.

The Pull Request draft

Gitee now supports the ability to submit a draft PR when project members have not completed their developmentCreate the Pull Request draft.



Also, the ability to use PR drafts also helps to have other members check your Fork for feedback,

A PR submitted in draft form will be prompted on the relevant pages of the PR and cannot be merged. When ready for code review, the PR can be removed from draft status and normal code review and merge will take place.

GPG features complete

Gitee already supports the use of GPG public keys. Click here to see how to use GPG on Gitee.

Recently, the Gitee team has also made improvements to gPG-related features, including the following updates:

  • When a Pull Request is created, the Commit list can display the GPG flag.
  • The platform submits/merges codes through Web pages, and supports automatic addition of platform GPG signatures.
  • Optimization of GPG signature prompt card copywriting on the existing platform;
  • Support for identifying GPG signatures from other third-party SaaS.

The above functional updates have been fully online in Gitee Community edition and Enterprise edition. If you have more problems and suggestions in the use of Gitee Feedback warehouse, please feel free to Feedback to us: gitee.com/oschina/git… .