Edits history of script submission #1293 for ' Update the branching model config for a repository (bitbucket)'

• nativets

  Ap­pro­ved version

  Edit in Windmill

  Embed

  type Bitbucket = {
    username: string;
    password: string;
  };
  /**
   * Update the branching model config for a repository
   * Update the branching model configuration for a repository.
   */
  export async function main(
    auth: Bitbucket,
    repo_slug: string,
    workspace: string
  ) {
    const url = new URL(
      `https://api.bitbucket.org/2.0/repositories/${workspace}/${repo_slug}/branching-model/settings`
    );
  
    const response = await fetch(url, {
      method: "PUT",
      headers: {
        Authorization: "Basic " + btoa(`${auth.username}:${auth.password}`),
      },
      body: undefined,
    });
    if (!response.ok) {
      const text = await response.text();
      throw new Error(`${response.status} ${text}`);
    }
    return await response.json();
  }
  

  Submitted by hugo697 375 days ago

• nativets

  Edit in Windmill

  Embed

  type Bitbucket = {
    username: string;
    password: string;
  };
  /**
   * Update the branching model config for a repository
   * Update the branching model configuration for a repository.
   */
  export async function main(
    auth: Bitbucket,
    repo_slug: string,
    workspace: string
  ) {
    const url = new URL(
      `https://api.bitbucket.org/2.0/repositories/${workspace}/${repo_slug}/branching-model/settings`
    );
  
    const response = await fetch(url, {
      method: "PUT",
      headers: {
        Authorization: "Basic " + btoa(`${auth.username}:${auth.password}`),
      },
      body: undefined,
    });
    if (!response.ok) {
      const text = await response.text();
      throw new Error(`${response.status} ${text}`);
    }
    return await response.json();
  }
  

  Submitted by hugo697 935 days ago

• nativets

  Edit in Windmill

  Embed

  type Bitbucket = {
    username: string;
    password: string;
  };
  /**
   * Update the branching model config for a repository
   * Update the branching model configuration for a repository.
  
  The `development` branch can be configured to a specific branch or to
  track the main branch. When set to a specific branch it must
  currently exist. Only the passed properties will be updated. The
  properties not passed will be left unchanged. A request without a
  `development` property will leave the development branch unchanged.
  
  It is possible for the `development` branch to be invalid. This
  happens when it points at a specific branch that has been
  deleted. This is indicated in the `is_valid` field for the branch. It is
  not possible to update the settings for `development` if that
  would leave the branch in an invalid state. Such a request will be
  rejected.
  
  The `production` branch can be a specific branch, the main
  branch or disabled. When set to a specific branch it must currently
  exist. The `enabled` property can be used to enable (`true`) or
  disable (`false`) it. Only the passed properties will be updated. The
  properties not passed will be left unchanged. A request without a
  `production` property will leave the production branch unchanged.
  
  It is possible for the `production` branch to be invalid. This
  happens when it points at a specific branch that has been
  deleted. This is indicated in the `is_valid` field for the branch. A
  request that would leave `production` enabled and invalid will be
  rejected. It is possible to update `production` and make it invalid if
  it would also be left disabled.
  
  The `branch_types` property contains the branch types to be updated.
  Only the branch types passed will be updated. All updates will be
  rejected if it would leave the branching model in an invalid state.
  For branch types this means that:
  
  1. The prefixes for all enabled branch types are valid. For example,
     it is not possible to use '*' inside a Git prefix.
  2. A prefix of an enabled branch type must not be a prefix of another
     enabled branch type. This is to ensure that a branch can be easily
     classified by its prefix unambiguously.
  
  It is possible to store an invalid prefix if that branch type would be
  left disabled. Only the passed properties will be updated. The
  properties not passed will be left unchanged. Each branch type must
  have a `kind` property to identify it.
  
  There is currently a side effect when using this API endpoint. If the
  repository is inheriting branching model settings from its project,
  updating the branching model for this repository will disable the
  project setting inheritance.
  
  
  We have deprecated this side effect and will remove it on 1 August 2022.
   */
  export async function main(
    auth: Bitbucket,
    repo_slug: string,
    workspace: string
  ) {
    const url = new URL(
      `https://api.bitbucket.org/2.0/repositories/${workspace}/${repo_slug}/branching-model/settings`
    );
  
    const response = await fetch(url, {
      method: "PUT",
      headers: {
        Authorization: "Basic " + btoa(`${auth.username}:${auth.password}`),
      },
      body: undefined,
    });
    if (!response.ok) {
      const text = await response.text();
      throw new Error(`${response.status} ${text}`);
    }
    return await response.json();
  }
  

  Submitted by hugo697 935 days ago