openapi-github 0.1.0

/*
 * GitHub's official OpenAPI spec + Octokit extension
 *
 * OpenAPI specs from https://github.com/github/rest-api-description with the 'x-octokit' extension required by the Octokit SDKs
 *
 * The version of the OpenAPI document: 16.6.0
 * 
 * Generated by: https://openapi-generator.tech
 */

use crate::models;
use serde::{Deserialize, Serialize};

#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct GitCreateTreeRequest {
    /// Objects (of `path`, `mode`, `type`, and `sha`) specifying a tree structure.
    #[serde(rename = "tree")]
    pub tree: Vec<models::GitCreateTreeRequestTreeInner>,
    /// The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by `base_tree` and entries defined in the `tree` parameter. Entries defined in the `tree` parameter will overwrite items from `base_tree` with the same `path`. If you're creating new changes on a branch, then normally you'd set `base_tree` to the SHA1 of the Git tree object of the current latest commit on the branch you're working on. If not provided, GitHub will create a new Git tree object from only the entries defined in the `tree` parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit's tree and were not defined in the `tree` parameter will be listed as deleted by the new commit. 
    #[serde(rename = "base_tree", skip_serializing_if = "Option::is_none")]
    pub base_tree: Option<String>,
}

impl GitCreateTreeRequest {
    pub fn new(tree: Vec<models::GitCreateTreeRequestTreeInner>) -> GitCreateTreeRequest {
        GitCreateTreeRequest {
            tree,
            base_tree: None,
        }
    }
}