---
title: "Power Editor for Bitbucket workflow"
canonical: "https://support.appfire.com/space/EDITOR/149979176/Power%20Editor%20for%20Bitbucket%20workflow"
format: markdown
---
> Macro (aura-html)

Once Power Editor has been successfully downloaded and the license applied, you can create a new file, upload an existing file from another location, or edit a file in your repository. 

### Create or upload a new file to your repository

#### To create a new file:

Click **New File** > **Create New File** to create a new file. Enter a filename and extension type in the **Filename** field above the editor, for example, `README.MD`.

![image](media://8e818716-3dc7-4993-87a3-0f6edf0052fb)

Provide content to the file using the editor.

![image](media://ad6e73d1-a065-4fbf-8d51-dd2267be2a3c)

#### To upload a file:

Click **New File **> **Upload File **to upload a file from another location. When the File Upload to / page opens, drag a file into the **Drop files here… **box or click **choose your files** and navigate to the file location, select the file and click **Open**.

![image](media://f9765550-d30e-4777-a868-2b0ea8f1b368)

Select **Commit directly to the branch **or **Branch and start a pull request **and click **Commit**. The file appears in your repository.

### Edit an existing file

Click on a file from your repository and click **Edit** to open that file in the editor. For an existing README file, you can also click **Edit README.**

The editor opens with the command bar along the top of the editor:

![Power Editor command bar](media://290bbc8d-7685-4318-86aa-96f8053d4c4c)

The image below shows an example of each formatting type. 

Set the indent by selecting **Spaces** or **Tabs** from the **Indent mode** dropdown and choose the number of spaces from the **Spaces** dropdown.

To see what the file looks like with the formatting, click **Preview**.

To review the available shortcuts in Power Editor, click **?.**

![image](media://937e18c4-95ba-4155-b3b7-6b3c25590329)

You can look at an online [https://www.markdownguide.org/](https://www.markdownguide.org/) for more information that can help with using Markdown formatting.

When you have finished making the changes to the file, click **Commit** and select **Commit directly to the branch** or **Branch and start a pull request**. Click **Commit Changes**. 

![image](media://41c1df25-77af-4baa-98dc-89009c02d519)

### Rename file

To rename a file:

Select the file from the Source list and click **… **> **Rename**.

![image](media://c0890d4f-79e5-48ca-aa01-9a65e8670880)

Enter a new file name in the **New path** field.

Enter a message in the **Commit message** field or leave the default message.

Select the **Create a pull request for this change** option if required.

![image](media://326a1a79-c079-44b8-a603-598660a27b2a)

Click **Commit**.

### Delete file

To delete a file:

 Select the file from the Source list and click `...`** **> **Delete**.

![image](media://51e1dcba-4cff-4fd0-b7ce-1fcba931ba83)

Enter a message in the **Commit message** field or leave it the default message.

Select the **Create a pull request for this change** option if required.

![image](media://66629c2b-dcb9-4d7d-89b7-4af4464ab757)

Click **Commit**.

## Resolve Conflict

When there is a conflict between the target and source files, you cannot merge a pull request until the conflict is fixed. The Resolve conflict feature allows you to 

1. Click **Create pull request **from the Bitbucket menu on the left side of the page.
2. Select the Source and Destination branches for the pull request and click **Continue**.
3. Enter a name for the pull request and a description, select your reviewers and click **Create**. When a conflict occurs, the **Resolve Conflict **button appears in the top right corner.
4. Click **Resolve conflict **to open the editor and display the file containing the file content from both branches. Manually make the change to the file and click **Commit** to commit the file to the source branch, or click **Merge to Destination** to merge the updated file to the destination branch.
5. Once you have resolved the conflict, you can merge the branches.

## Additional resources

- [https://appfire.atlassian.net/wiki/spaces/EDITOR/pages/149979247](https://appfire.atlassian.net/wiki/spaces/EDITOR/pages/149979247)
- [https://appfire.atlassian.net/wiki/spaces/EDITOR/pages/149979255](https://appfire.atlassian.net/wiki/spaces/EDITOR/pages/149979255)
- [https://appfire.atlassian.net/wiki/spaces/EDITOR/pages/149979242](https://appfire.atlassian.net/wiki/spaces/EDITOR/pages/149979242)