feat(api): add comprehensive repository management API endpoints
- Introduce new repo module with complete repository functionality - Add endpoints for repository CRUD operations (create, get, update, archive, delete) - Implement branch management with create, list, delete and protection features - Add tag management with create, list and delete operations - Include release management with create, update and delete capabilities - Support repository forking with sync functionality - Implement starring and watching mechanisms for repositories - Add member management with roles and invitations - Provide deploy key management for CI/CD integration - Create webhook management for external integrations - Implement branch protection rules with approval requirements - Add commit status and comment functionality for code reviews - Include merge checking logic for pull requests - Register all new endpoints in OpenAPI documentation - Configure routes to handle new repository-specific paths
This commit is contained in:
@@ -0,0 +1,69 @@
|
||||
use actix_web::{web, HttpResponse};
|
||||
use serde::Deserialize;
|
||||
use utoipa::IntoParams;
|
||||
|
||||
use crate::api::response::{ApiResponse, ApiErrorResponse};
|
||||
use crate::error::AppError;
|
||||
use crate::models::repos::Repo;
|
||||
use crate::service::AppService;
|
||||
use crate::session::Session;
|
||||
|
||||
#[derive(Debug, Deserialize, IntoParams)]
|
||||
pub struct PathParams {
|
||||
/// Workspace name (unique identifier)
|
||||
pub workspace_name: String,
|
||||
/// Repository name (unique within the workspace)
|
||||
pub repo_name: String,
|
||||
}
|
||||
|
||||
use crate::service::repo::fork::ForkRepoParams;
|
||||
|
||||
/// Fork a repository
|
||||
///
|
||||
/// Creates a copy of the repository in the specified workspace or the current user's workspace.
|
||||
/// Requires read access to the source repository and write access to the target workspace.
|
||||
///
|
||||
/// Effects:
|
||||
/// - Creates a new repository with all branches, tags, and commit history
|
||||
/// - Establishes a parent-child relationship between source and fork
|
||||
/// - Fork is initially set to private visibility
|
||||
/// - Current user becomes the owner of the fork
|
||||
///
|
||||
/// Returns the created fork repository with full metadata.
|
||||
#[utoipa::path(
|
||||
post,
|
||||
path = "/api/v1/workspaces/{workspace_name}/repos/{repo_name}/fork",
|
||||
tag = "Repos",
|
||||
operation_id = "repoFork",
|
||||
params(PathParams),
|
||||
request_body(
|
||||
content = ForkRepoParams,
|
||||
description = "Fork parameters (all fields optional)",
|
||||
content_type = "application/json"
|
||||
),
|
||||
responses(
|
||||
(status = 201, description = "Repository forked successfully. Returns the newly created fork with full metadata.", body = ApiResponse<Repo>),
|
||||
(status = 400, description = "Invalid parameters: target name conflicts or invalid characters", body = ApiErrorResponse),
|
||||
(status = 401, description = "Authentication required or session expired", body = ApiErrorResponse),
|
||||
(status = 403, description = "Insufficient permissions to fork or create in target workspace", body = ApiErrorResponse),
|
||||
(status = 404, description = "Source repository or target workspace not found", body = ApiErrorResponse),
|
||||
(status = 409, description = "Fork with this name already exists in target workspace", body = ApiErrorResponse),
|
||||
(status = 500, description = "Internal server error or Git operation failed", body = ApiErrorResponse),
|
||||
),
|
||||
security(
|
||||
("session_cookie" = [])
|
||||
)
|
||||
)]
|
||||
pub async fn fork_repo(
|
||||
service: web::Data<AppService>,
|
||||
session: Session,
|
||||
path: web::Path<PathParams>,
|
||||
params: web::Json<ForkRepoParams>,
|
||||
) -> Result<HttpResponse, AppError> {
|
||||
let repo = service
|
||||
.repo
|
||||
.repo_fork(&session, &path.workspace_name, &path.repo_name, params.into_inner())
|
||||
.await?;
|
||||
|
||||
Ok(HttpResponse::Created().json(ApiResponse::new(repo)))
|
||||
}
|
||||
Reference in New Issue
Block a user