refactor(api): reorder imports and update code formatting across repository endpoints
- Reordered actix-web imports to standardize import order - Reordered crate module imports to follow alphabetical ordering - Updated function calls to use multi-line formatting for better readability - Standardized blank lines around documentation comments - Applied consistent formatting to response handling methods - Normalized import organization across all repository-related API files - Improved code consistency and maintainability through standardized formatting - Applied formatting updates to all repository endpoint implementations
This commit is contained in:
@@ -1,12 +1,12 @@
|
||||
use actix_web::{web, HttpResponse};
|
||||
use actix_web::{HttpResponse, web};
|
||||
use serde::Deserialize;
|
||||
use utoipa::IntoParams;
|
||||
|
||||
use crate::api::response::{ApiResponse, ApiErrorResponse};
|
||||
use crate::api::response::{ApiErrorResponse, ApiResponse};
|
||||
use crate::error::AppError;
|
||||
use crate::models::repos::RepoCommitStatus;
|
||||
use crate::service::repo::commit_status::CreateCommitStatusParams;
|
||||
use crate::service::AppService;
|
||||
use crate::service::repo::commit_status::CreateCommitStatusParams;
|
||||
use crate::session::Session;
|
||||
|
||||
#[derive(Debug, Deserialize, IntoParams)]
|
||||
@@ -21,19 +21,19 @@ pub struct PathParams {
|
||||
///
|
||||
/// Creates a new status check for a specific commit, typically used by CI/CD systems.
|
||||
/// Requires Write role or higher in the repository.
|
||||
///
|
||||
///
|
||||
/// Parameters:
|
||||
/// - commit_sha: Commit SHA to attach the status to (must exist in repository)
|
||||
/// - state: Status state ("pending", "success", "failure", "error")
|
||||
/// - context: Status context name (e.g., "ci/build", "ci/test") - must be unique per commit
|
||||
/// - description: Human-readable description of the status (optional, max 500 characters)
|
||||
/// - target_url: URL with detailed information about the status (optional)
|
||||
///
|
||||
///
|
||||
/// Effects:
|
||||
/// - Status is attached to the commit
|
||||
/// - Can be used by branch protection rules to enforce status checks
|
||||
/// - Multiple statuses can exist for the same commit with different contexts
|
||||
///
|
||||
///
|
||||
/// Returns the created status with metadata including ID and timestamps.
|
||||
#[utoipa::path(
|
||||
post,
|
||||
@@ -67,7 +67,12 @@ pub async fn create_commit_status(
|
||||
) -> Result<HttpResponse, AppError> {
|
||||
let status = service
|
||||
.repo
|
||||
.repo_create_commit_status(&session, &path.workspace_name, &path.repo_name, params.into_inner())
|
||||
.repo_create_commit_status(
|
||||
&session,
|
||||
&path.workspace_name,
|
||||
&path.repo_name,
|
||||
params.into_inner(),
|
||||
)
|
||||
.await?;
|
||||
|
||||
Ok(HttpResponse::Created().json(ApiResponse::new(status)))
|
||||
|
||||
Reference in New Issue
Block a user