Easily create and assign Issues directly from the Epic itself Plan and track features and work group level epics that collect issues together. Issue board lists that pull in issues in a given milestoneĪssign scoped labels mutually exclusively when they have the same scope.Īssign more than one person to an issue at a time. Visualize multiple epics and milestones across time in a roadmap view. Templates for a Group to make consistency easier.Īn overview of all the projects, environments provisioned and the numbers of pods used by each environment in a Kubernetes cluster. Visualize cross-project environments, track change flow from development to production, track pipeline status and diagnose issues from a single dashboard.ĭefine custom LICENSE. Manage the deployments and connection to your Kubernetes clusters in a secure and compliant way, driven by code. The power of GitLab CI/CD pipelines to build, test, and deploy your applications easily. Reduce pipeline queueing and waiting time with merge trains which allows parallel pipeline execution, with each pipeline building off the merge result of the previous one.Ĭonnect your projects hosted on external services (like GitHub or Bitbucket) and leverage Visualize how pipelines across projects are linked together, including cross project dependencies. Visualize the history and current status of pipelines across projects and groups all in a single dashboard that can be customized for each user. Through a form in your review app - which is then automatically added to the related merge request Shorten the feedback cycle and enable stakeholders to provide comments A special pipeline runs on the results of merged code before merging into master to detect changes that may be green on a branch but will fail master when merged.įull Code Quality reports are available on the pipeline page, showing areas of the codebase that do not meet the organization’s preferred style or standards. Code owners are assignedĪutomatically as merge request approvers.įind bottlenecks in your code review process by understanding how long open merge requests have been in review. Number of users to approve of a merge request before it is able to beįor faster code review, draft multiple comments in a merge request code review,īefore submitting them together all at once.Īssign Code Owners to files to indicate the team members responsible forĬode in your project. To ensure strict code review, you can require a minimum
0 kommentar(er)
