Rename project to go-mimedb
I was testing to see if I could create a new project under gitlab-org
so I added the test-
prefix to the name.
Only maintainers have access to the settings so I can't rename this project
Create new project checklist
https://about.gitlab.com/handbook/engineering/#creating-a-new-project
-
Ensure that the project is under the gitlab-org namespace (or a subgroup of it when relevant) for anything related to the application or under the gitlab-com namespace for anything strictly company related. -
Configure the project repository to use main as the name of the default branch. -
Add the project to the list of GitLab projects. gitlab-com/www-gitlab-com!63816 (merged) -
Add a license to the repository. Contact #legal as to which license to add. A sample license is here: gitlab-org/gitlab MIT License, but contact legal before using it. !2 (merged) -
Add a section titled "Developer Certificate of Origin and License" to CONTRIBUTING.md in the repository. It is easiest to simply copy-paste the gitlab-org/gitlab DCO + License section verbatim. !3 (merged) -
Add any further relevant details to the Contribution Guide. See Contribution Example. -
Add a link to CONTRIBUTING.md from the project's README.md. !3 (merged) -
Add a CODEOWNERS file, to make it easy for contributors to figure out which teams are best suited to review their changes. !4 (merged) -
Use teams rather than individuals as owners, to make it self updating over time and resilient to people taking time off -
You can scope ownership to subdirectories or individual files, but it should contain at the very least a top-level catch all for any new or non explicitly mentionned file.
-
-
When possible, projects should have the following Merge request settings enabled: -
Merge Trains. -
Delete source branch after merge. -
Merge only if pipeline succeeds. -
Merge only when all threads are resolved.
-
-
When possible, projects should have the following Pipeline settings enabled: -
Auto-cancel pending pipelines.
-
-
If needed, make sure to set up a default CI/CD configuration. -
If your project contains code that is distributed with GitLab or is executed in production, set up security jobs for your project and add your project to the AppSec team's triage rotation. The AppSec will triage security findings from the Security Dashboard and create issues for vulnerabilities.
Edited by Vladimir Shushlin