GitLab integration

Fortiana can use GitLab repository changes, issues, code reviews and comments to answer questions about regressions, revisions and earlier implementation decisions.

What is GitLab?

GitLab provides tools across the software development lifecycle, from code creation and repository history to issue tracking, merge requests, review, and CI/CD. A GitLab project groups a repository with collaboration, project-management, and delivery capabilities.

How it works with Fortiana

A regression can reopen a discussion from an earlier implementation. GitLab gives that question a history: the change, the issue it addressed and the feedback raised during review. Fortiana can use these records together when the explanation is spread across several parts of the development conversation.

What Fortiana can use

  • Repositories and changes
  • Issues and code reviews
  • Comments and review history

Not included: A full copy of every repository file.

How you can use it

For example, you can ask questions such as:

  • Which change is linked to this regression?
    Compare the relevant change and issue discussion to understand when the failing behavior was first described.
  • What concern was raised during review?
    Use review comments to recover the risk or alternative the team discussed before accepting the change.
  • Have we tried this fix before?
    Look for earlier changes and issues that describe the same approach and the team’s response.

Before you connect

  • Identify the repositories. List the GitLab repositories and issue history relevant to the first connection.
  • Confirm access requirements. Identify the repository owner who can review the connection requirements and the intended access.
  • Separate history from file contents. Check whether your questions need the review trail or complete source files; a full repository clone is outside this connection.
All integrations