Let's talk about Gitee's warehouse hiding function
Gitee is a popular online code hosting platform in China, providing a series of services such as Git warehouse management, code contribution, and document management. When using Gitee, sometimes we want to hide a certain warehouse. Today we will introduce Gitee's warehouse hiding function.
1. The hidden role of the warehouse
The warehouse created on Gitee is public by default, that is, any visitor can see the warehouse and obtain all the contents in the warehouse, including code and documents. , Issue, etc. This is likely to cause some security risks, such as source code leakage, private information leakage, etc. To avoid this risk, when creating a repository on Gitee, we can choose to hide it.
2. How to hide the warehouse
- Log in to your Gitee account and enter the warehouse page that needs to be hidden.
- Click the "Settings" button in the upper right corner to enter the warehouse settings page ,
- In the "Basic Information" tab, find the "Visibility" option and change it to "Private" or "Internal".
- After saving the settings, the warehouse will become Is private or internal and can only be accessed by invited members.
3. The difference between private and internal
- Private warehouse: Only the creator and invited members can see the warehouse and its contents, and cannot be explored by non-invited members to and visit.
- Internal warehouse: Only members of the organization (including the creator) can see the warehouse and its contents. Members of the organization can discover and access the warehouse through the member list in the organization.
4. How to invite members
- On the warehouse page that needs to be invited, click the "Settings" button on the right, and
- enter the warehouse settings page , click the "Member Management" tab on the left,
- In the member management page, fill in or search for the Gitee account username of the member who needs to be invited, and select the role to be invited,
- Click "Invite" will send an invitation to the account, and you can access the warehouse after waiting for the other party's confirmation.
5. Notes
- Hiding a warehouse only changes it from a public state to a private or internal state. It is recommended that you still set appropriate access permissions to manage the content in the warehouse. ;
- When inviting members, it is recommended to only invite necessary members to participate in the project to prevent leakage of project information.
The above is the introduction and operation method of Gitee warehouse hiding. I hope it will be helpful to everyone!
The above is the detailed content of Let's talk about Gitee's warehouse hiding function. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Git is a version control system, and GitHub is a Git-based code hosting platform. Git is used to manage code versions and supports local operations; GitHub provides online collaboration tools such as Issue tracking and PullRequest.

Git and GitHub are not the same thing. Git is a version control system, and GitHub is a Git-based code hosting platform. Git is used to manage code versions, and GitHub provides an online collaboration environment.

GitHub is not difficult to learn. 1) Master the basic knowledge: GitHub is a Git-based version control system that helps track code changes and collaborative development. 2) Understand core functions: Version control records each submission, supporting local work and remote synchronization. 3) Learn how to use: from creating a repository to push commits, to using branches and pull requests. 4) Solve common problems: such as merge conflicts and forgetting to add files. 5) Optimization practice: Use meaningful submission messages, clean up branches, and manage tasks using the project board. Through practice and community communication, GitHub’s learning curve is not steep.

On your resume, you should choose to write Git or GitHub based on your position requirements and personal experience. 1. If the position requires Git skills, highlight Git. 2. If the position values community participation, show GitHub. 3. Make sure to describe the usage experience and project cases in detail and end with a complete sentence.

Microsoft does not own Git, but owns GitHub. 1.Git is a distributed version control system created by Linus Torvaz in 2005. 2. GitHub is an online code hosting platform based on Git. It was founded in 2008 and acquired by Microsoft in 2018.

Starting from Git is more suitable for a deep understanding of version control principles, and starting from GitHub is more suitable for focusing on collaboration and code hosting. 1.Git is a distributed version control system that helps manage code version history. 2. GitHub is an online platform based on Git, providing code hosting and collaboration capabilities.

The reason for using GitHub to manage HTML projects is that it provides a platform for version control, collaborative development and presentation of works. The specific steps include: 1. Create and initialize the Git repository, 2. Add and submit HTML files, 3. Push to GitHub, 4. Use GitHubPages to deploy web pages, 5. Use GitHubActions to automate building and deployment. In addition, GitHub also supports code review, Issue and PullRequest features to help optimize and collaborate on HTML projects.

Git is an open source distributed version control system that helps developers track file changes, work together and manage code versions. Its core functions include: 1) record code modifications, 2) fallback to previous versions, 3) collaborative development, and 4) create and manage branches for parallel development.
