testeiya 0.2.0 → 0.3.9

package/skills/testeiya/testomatio-docs/docs/advanced/branches-folder/index.md

@@ -1,277 +0,0 @@
----
-title: Branches
-description: Learn how to manage test branching in Testomat.io for efficient collaboration. This guide covers creating branches for isolated test modifications, working within branches without affecting the main test suite, handling automated tests in branches, and merging or replacing changes to the main branch. It also explains the difference between merging and replacing branches to maintain version control in testing.
-type: article
-url: https://docs.testomat.io/advanced/branches-folder
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/131321183-37ad9b3e-9e8f-43e6-9860-205168095580.DNfdbGhq_1ithLh.webp
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Testomat.io branches, test branching, test versioning, merge branches, revert merge, automated tests, test suites, version control, collaborative testing, test management, QA
----
-
-The typical day-to-day workflow includes constant code changes made by developers. As the code evolves, quality assurance teams must update tests to maintain accurate test coverage. You may need to add tests for a new feature without affecting existing suites, or your team may include multiple specialists who need to work independently.
-
-For all these cases, Testomat.io provides **test branching and versioning** — allowing teams to work on isolated changes without impacting each other or the Main branch.
-
-These are the core actions available when working with branches:
-
-- Create new branches (including directly from [Jira](https://docs.testomat.io/advanced/jira-plugin/branches/))
-- Switch between branches
-- Compare changes with Main (Diff)
-- Merge changes to Main (excluding diverged items)
-- Replace changes in Main (including diverged items)
-- Revert a merge (branch returns to Active)
-- Delete a branch permanently
-
-## Supported Merge Changes
-
-Here’s a quick overview of what changes are **supported** in Testomat.io branches and will be merged into Main:
-
-- **CRUD actions** in folders, suites, and tests
-- **Labels** (assign / unassign)
-- **Tags** (assign / unassign)
-- **Attachments** (add to the **test body** or delete)
-- **Jira issue linking** (link / unlink)
-- **CRUD actions** in **comments**
-
-## How to Create a Branch
-
-1. Navigate to the **Branches** page
-2. Enter a branch title
-3. Click the **Create** button
-
-![Create a new branch](./images/att1_348.png)
-
-Your new branch will appear under the **Active** tab. You can create as many branches as needed and switch between them at any time.
-
-![Created branch](./images/att2_348.png)
-
-## How to Work within a Branch
-
-After creating a branch, switch to it to start working.
-
-### Switch to a Branch
-
-1. Click **'...'** menu next to the created branch
-2. Click the **Switch to this branch** button
-
-![Switch to the branch](./images/att3_348.png)
-
-Alternative way to switch to a branch:
-
-1. Open the created branch
-2. Click **Switch to Branch** button
-
-![Switch to Branch](./images/att4_348.png)
-
-Inside the branch, you can manage folders, suites, and tests. All new or modified items are marked with a badge.
-
-:::note
-
-**Drag & Drop** and the **Move** option are disabled in branches to prevent potential data loss and accidental structural conflicts.
-
-:::
-
-While working in a branch, the **current branch name** is displayed as a **badge in the bottom-right corner** of the any page. Clicking this badge takes you directly to the **Branches** page and highlights the current branch, allowing you to quickly **compare it with Main**.
-
-![*badge in the bottom-right corner](./images/gif1_348.gif)
-
-### Automated Tests in Branches
-
-When testing different versions of your software you may need to add automated tests to a specific branch for some reason. Testomat.io allows working with automated tests within a branch, separately from Main:
-
-- create a new branch during import using `TESTOMATIO_BRANCH` parameter, learn more [here](https://docs.testomat.io/project/import-export/import/import-js/#import-into-a-branch)
-- import tests into a chosen branch, learn more [here](https://docs.testomat.io/project/import-export/import/)
-
-![import automated tests](./images/att5_348.png)
-
-### Switch Back to Main
-
-If you need to switch back to Main before merging, you can do it from the **Branches** page:
-
-![Branches page](./images/att11_348.png)
-
-Or from a specific branch:
-
-1. Navigate to the **Branches** page
-2. Open the **Active** tab
-3. Click the branch you need
-4. Click the **Switch to Main** button
-
-![Switch to Main](./images/att10_348.png)
-
-## Compare Changes with Main
-
-You can compare changes with **Main**:
-
-1. Navigate to the **Branches** page
-2. Open the **Active** tab
-3. Click the branch you want to compare:
-
-- **Test Changes** tab – displays changes at the individual test
-- **Suite Changes** tab – displays changes at the suite level
-- **Structure** tab – displays all changes to the structure using a side-by-side diff view
-
-4. Open the test/suite you want to compare
-
-See the **diff** for a test or suite between Main and the current branch.
-
-![Diff between Main and branch](./images/att9_348.png)
-
-## Merge and Replace to Main
-
-After completing work in a branch, you can **merge** or **replace** your changes in Main.
-
-### Merge a Branch
-
-1. Navigate to the **Branches** page
-2. Open the branch you want to merge
-3. Click the **Merge** dropdown
-4. Select the **Merge** button
-
-![Merge branch](./images/att14_348.png)
-
-### Replace a Branch
-
-1. Navigate to the **Branches** page
-2. Open the branch you want to replace
-3. Click the **Merge** dropdown
-4. Select the **Replace** button
-
-![Replace branch](./images/att15_348.png)
-
-## Difference between Merge and Replace
-
-- **Merge**: applies all changes from the current branch **except diverged tests and suites**. Only modifications made in the branch are merged into Main.
-
-- **Replace**: applies all changes from the current branch, **including diverged tests and suites**. This fully replaces Main with the branch, so the Main can be off-track.
-
-## Merging Tests with Parameters (Examples)
-
-When merging a branch into Main, Testomat.io also carries over **test parameters** — the example data tables attached to parametrized test cases. See [Classical Tests Markdown Format — Examples](https://docs.testomat.io/project/import-export/export-tests/classical-tests-markdown-format/#examples) for details on how parameters are structured.
-
-### Choosing the Right Merge Option for Parameters
-
-| Situation                                             | Recommended action |
-| ----------------------------------------------------- | ------------------ |
-| Test with Parameters Created in a Branch              | **Merge**          |
-| Test Created in Main, Parameters Modified in a Branch | **Replace**        |
-
-:::note
-
-**Replace** applies to the entire branch, not just the parametrized tests. Any other diverged tests or suites in the branch will also overwrite their **Main** counterparts. Review the diff carefully before using **Replace** to make sure you're not accidentally overriding unrelated changes.
-
-:::
-
-### Scenario 1: Test with Parameters Created in a Branch
-
-If a test case — including its parameters — was **first created inside a branch**, merging that branch into Main works as expected out of the box.
-
-- Use the standard **Merge** option
-- The test case and its full example table are brought into Main automatically
-- No special handling is required
-
-**Example workflow:**
-
-1. Create a new branch `feature/login-params` and switch to it
-2. In the branch, create a new test **"Login with multiple roles"** and add an examples table with rows for `admin`, `editor`, and `viewer`
-3. Open the branch compare view and click **Merge → Merge**
-4. The test and all its examples appear in Main
-
-![ Test with Parameters Created in a Branch](./images/gif1_1485.gif)
-
-### Scenario 2: Test Created in Main, Parameters Modified in a Branch
-
-If a test case already exists in Main and you need to update its parameters in a branch (add, remove, or change example rows), use **Replace instead of Merge**. Replace is designed exactly for this: it applies all branch changes — including updated parameters — directly into Main, giving you full control over how parameterized tests evolve across branches.
-
-**Example workflow:**
-
-1. A test **"Checkout with payment methods"** exists in **Main** with two example rows: `credit_card` and `paypal`
-2. Create a new branch `update/checkout-params` and switch to it
-3. Add a third row: `apple_pay` to that test's examples table
-4. Open the branch compare view:
-
-- the view may appear empty if **only** parameters were changed
-- or show other edits if the test body was also modified
-
-5. Click **Merge → Replace** to apply the updated parameters to **Main**
-
-![Test Created in Main, Parameters Modified in a Branch](./images/gif2_1485.gif)
-
-## Revert Merge
-
-If a merge caused unintended changes or issues, you can **revert a merge** using one of the following methods:
-
-### From the Branches Page
-
-1. Navigate to the **Branches** page
-2. Open the **Merged** tab
-3. Find the branch you want to revert
-4. Click **Revert Merge** button
-
-![Revert Merge](./images/att7_348.png)
-
-### From the Pulse Page
-
-You can also revert a merge directly from the project activity log:
-
-1. Navigate to the **Pulse** page
-2. Find and open the merged branch entry labeled **Bulk edit applied**
-3. Click the **Rollback** button
-
-![Rollback button](./images/att8_348.png)
-
-After the revert/rollback:
-
-- the branch returns to the **Active** tab
-- all merged changes are undone
-- a new log entry appears **Bulk edit applied → Restored bulk operation** in Pulse
-
-This log confirms that the merge has been successfully reverted.
-
-## Working with Forks
-
-When the same test is modified in different branches, Testomat.io automatically creates **Forks**. You can switch between the original item and its forks at any time from this tab.
-
-1. Navigate to the **Tests** page
-2. Open the desired test
-3. Open the **Forks** tab
-4. Click the **Switch to it** button
-
-This makes it easy to track differences between branches and navigate to the version you need.
-
-![Forks](./images/att6_348.png)
-
-## How to Delete a Branch
-
-You can delete branches when they are no longer needed.
-
-### Delete a Single Branch
-
-1. Navigate to the **Branches** page
-2. Open the **Active** or **Merged** tab
-3. Click the **'...'** menu next to the branch you want to delete
-4. Select **Delete** button
-
-![Delete single button](./images/att12_348.png)
-
-### Delete All Merged Branches
-
-1. Navigate to the **Branches** page
-2. Open the **Active** or **Merged** tab
-3. Click the **'...'** menu in the **top-right corner** of the tab
-4. Select **Delete All Merged Branches**
-
-![Delete merged branches](./images/att13_348.png)
-
-:::note
-
-Deleting a branch is permanent and cannot be undone. Once deleted, the branch cannot be restored, and any previously merged changes cannot be reverted.
-
-:::

package/skills/testeiya/testomatio-docs/docs/advanced/bulk-edit-folder/bulk-edit-demos.mdx

@@ -1,39 +0,0 @@
----
-title: Bulk Edit Demo - Creating and Restructuring Tests with YAML
-description: Watch Bulk Edit in action with real-world examples. This page demonstrates how to create tests, remove a root suite, and restructure test projects in Testomat.io using YAML.
-type: article
-url: https://docs.testomat.io/advanced/bulk-edit-folder-demos
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/169832839-f67f3cad-73b7-43ff-ba00-b4ecd4296c2f.D7I3Huc-_Z21Q63i.webp
-      
-  - tag: meta
-    attrs:
-      name: keywords
-      content: bulk edit, test management, Testomat.io, YAML, test suite, reorder tests, create tests, delete tests, bulk test creation, file patterns, test restructuring, automation
----
-## Demos
-
-Let's see how powerful bulk edit mode is in action.
-
-### Creating Tests in Empty Suites
-
-This demo shows how to create multiple tests across different suites using the YAML editor. Instead of clicking through the UI, you can define everything in structured text and apply changes in bulk.
-
-import Bulk_edit_create_tests from "./images/Bulk_edit_create_tests.mp4"
-
-<video width="960" controls>
-  <source src={Bulk_edit_create_tests} type="video/mp4" />
-</video>
-
-### Replace Root Suite
-
-In cases where your project has only one root suite, you can simplify the structure by removing it. This demo shows how to flatten the hierarchy by moving all tests up one level.
-
-import change_root_suite from "./images/change_root_suite.mp4"
-
-<video width="960" controls>
-  <source src={change_root_suite} type="video/mp4" />
-</video>

package/skills/testeiya/testomatio-docs/docs/advanced/bulk-edit-folder/bulk-edit-on-suite-and-test-level.md

@@ -1,122 +0,0 @@
----
-title: Bulk Edit on Suite and Test Levels
-description: Learn how to use the Bulk Edit feature in Testomat.io to manage test suites more efficiently. This guide explains file and folder patterns, how to bulk edit individual suites using YAML, and how to quickly create multiple tests with minimal input.
-type: article
-url: https://docs.testomat.io/advanced/bulk-edit-folder-suites-and-tests
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/169832839-f67f3cad-73b7-43ff-ba00-b4ecd4296c2f.D7I3Huc-_Z21Q63i.webp
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: bulk edit, test management, Testomat.io, YAML, test suite, reorder tests, create tests, delete tests, bulk test creation, file patterns, test restructuring, automation
----
-
-## File and Folder Patterns
-
-In order to reflect the BDD paradigm in the best way and to support the consistency of the project structure, Testomat.io provides a Folder and File pattern.
-A suite with tests is considered to be a **file** (like a file with tests in your filesystem).
-A suite that contains other suites is a **folder** (like in a filesystem).
-So the main rule here is **suite can contain only tests or suites but not both**.
-
-## How to Use Bulk Edit on Suite Level
-
-Bulk Edit allows you to update an entire suite as a single Markdown document.
-
-Instead of opening tests one by one, you modify all tests directly inside the suite file. This speeds up large-scale updates and keeps test documentation consistent, especially for large regression suites or when multiple tests require the same change.
-
-### Why Use Bulk Edit
-
-In real QA workflows, updates rarely affect only one test. Bulk Edit is ideal for:
-
-- Updating or adding examples across multiple **parametrized tests**
-- Aligning labels, priorities, or tags across a feature area
-- Updating wording after UI changes
-- Refactoring test descriptions
-- Quickly drafting multiple new tests with the same description
-- Applying global text updates with **Change All Occurrences**
-
-By working at the suite level, all changes are applied automatically when the suite is saved, avoiding manual synchronization of individual tests. The editor works with the [Classical Tests Markdown Format](https://docs.testomat.io/project/import-export/export-tests/classical-tests-markdown-format/), where suites and tests are structured as blocks in a single Markdown document.
-
-:::note
-
-Deletions made in Bulk Edit are **not applied when saving** to prevent accidental removals. If you need to delete items, use the regular **multi-select** workflow instead.
-
-:::
-
-### Step-by-Step Guide
-
-1. Navigate to the **Tests** page
-2. Open the suite you want to edit
-3. Click the **'...'** extra menu
-4. Select the **'Bulk edit'**
-
-![Bulk Edit](./images/att1_541.png)
-
-5. The Markdown editor opens, displaying the full suite file
-
-From here, you can modify or create:
-
-- Suite metadata (emoji, overall tags, labels, assignees, etc.)
-- Test metadata (including tags, labels, priorities, assignees, etc.)
-- Test descriptions (steps, expected results, etc.)
-- Examples (parametrized tests)
-- Add a new test - either by clicking **Add Test** (which automatically inserts `<!-- test -->` and a new `##` block) or by writing it manually in the suite file
-
-![All changes in Bulk Edit](./images/att2_541.png)
-
-All changes follow the [Classical Tests Markdown Format](https://docs.testomat.io/project/import-export/export-tests/classical-tests-markdown-format/), so you can learn more about the structure and formatting rules.
-
-### Practical Example: Parametrized Tests
-
-**Scenario:** You need to update examples across multiple parametrized tests.
-
-**Without Bulk Edit:** Each test must be opened and updated individually.
-
-**With Bulk Edit:**
-
-1. Open the suite in Bulk Edit
-2. Select the parameters (examples) you want to update — they will be highlighted in the editor for easy identification
-3. Use **Change All Occurrences** to apply updates globally
-4. Update the parameters (examples)
-5. Click **Save**
-
-All tests instantly reflect the new or updated examples.
-
-![Markdown editor](./images/gif1_541.gif)
-
-Bulk Edit makes managing parametrized tests extremely efficient — whether adding new examples, correcting existing ones, or updating shared datasets.
-
-### Best Practices
-
-- Treat the suite file as a single source of truth for related tests
-- Make grouped, logical updates instead of many small edits
-- Review global replacements before saving
-- Keep formatting consistent to ensure correct parsing
-
-Bulk Edit works best for structured updates affecting multiple tests, rather than small individual corrections.
-
-## Bulk Tests Creation
-
-Sometimes, you may want to quickly add multiple test cases by name and save them for further completion. Our Bulk Tests Creation feature is intended to help you:
-
-1. Create a new or open existing test suite where your tests will be added.
-
-2. Enable the **Bulk** toggle to switch to bulk creation mode.
-
-3. Enter one test per line in the input field.
-
-4. Click **Create** to add all the tests at once.
-
-![CleanShot 2022-05-24 at 11 33 02@2x](./images/bulk_edit_toggle2.png)
-
-![CleanShot 2022-05-24 at 11 38 38@2x](./images/add_tests_click_create2.png)
-
-5. Your tests will appear immediately under the newly created suite.
-
-![CleanShot 2022-05-24 at 11 44 10@2x](./images/see_your_tests_created2.png)
-
-[![CleanShot 2022-05-27 at 20 19 26@2x](./images/170759254-e6d4379b-733e-4521-98f3-abccca6eaffa.jpg)](https://youtu.be/jnJwZsRQjTQ)

package/skills/testeiya/testomatio-docs/docs/advanced/bulk-edit-folder/what-is-bulk-edit.md

@@ -1,170 +0,0 @@
----
-title: Using Bulk Edit and YAML Format in Testomat.io
-description: Discover how to manage large test projects in Testomat.io using the Bulk Edit feature. Learn how to restructure test suites, create and delete tests using YAML format, preview changes, and use keyboard shortcuts for efficient test management.
-type: article
-url: https://docs.testomat.io/advanced/bulk-edit-folder
-head:
-  - tag: meta
-    attrs:
-      name: og:image
-      content: https://docs.testomat.io/_astro/169832839-f67f3cad-73b7-43ff-ba00-b4ecd4296c2f.D7I3Huc-_Z21Q63i.webp
-
-  - tag: meta
-    attrs:
-      name: keywords
-      content: bulk edit, test management, Testomat.io, YAML, test suite, reorder tests, create tests, delete tests, bulk test creation, file patterns, test restructuring, automation
----
-
-Bulk Edit is an advanced tool that allows to restructure tests within a project. With Bulk edit, you can
-
-- reorder tests
-- create new suites
-- move tests to another suite
-- delete tests
-
-## Enabling Bulk Edit
-
-Bulk edit mode can be opened from the Tests screen:
-
-![How to enable bulk edit in Testomat.io interface](./images/enabling_bulk_edit.png)
-
-:::note
-
-If your project contains **more than 1,000 tests**, the **Bulk Edit** button will be **disabled**.
-
-This limitation helps maintain optimal performance for very large projects.
-
-:::
-
-A bulk editor may look confusing at first:
-
-![Bulk editor overeview](./images/Bulk_editor_review.png)
-
-## Bulk Editor Overview
-
-The Bulk Editor provides a powerful interface for managing your project in a structured text format. Here's a breakdown of its key features:
-
-1. **Text-Based Editor** - Edit your project directly in YAML format for precise control and bulk updates.
-
-2. **Live Preview** - Instantly see a visual representation of your changes as you make them.
-
-3. **YAML Guide Link** - Access a quick reference guide to better understand and work with the YAML format.
-
-4. **‘Learn More’ Button** - Opens a mini-tutorial section with tips and examples for using the Bulk Editor effectively.
-
-5. **‘Read Docs’ Link** - Redirects you to the official [Testomatio documentation](<[https://docs.testomat.io/](https://docs.testomat.io/advanced/bulk-edit-folder/)>) for in-depth guidance.
-
-6. **‘Show Tests’ Toggle** - Switch between viewing both test suites and test cases or just the test suites.
-
-7. **‘Preview’ Button** - Displays a summary of your changes before applying them.
-
-   > _Note:_ Don't worry, clicking "Preview" won't execute any changes on the project. You will see the list of planned changes and a confirmation button to accept them.
-
-8. **‘Cancel’ Button** - Closes the editor and discards any unsaved changes.
-
-To make yourself comfortable with bulk editor follow the next sections:
-
-## YAML format
-
-We use [YAML format](https://yaml.org) to structure data. If you are not familiar with YAML, [learn its basics](https://docs.ansible.com/ansible/latest/reference_appendices/YAMLSyntax.html) before following the guide. The YAML format was chosen as the most popular for defining data structures in text-only mode. It is very powerful as you can edit a whole project from a text editor without extra clicking. YAML is used in Ansible, Kubernetes, CI configs, etc, so it is very popular in the developer community.
-
-## Working with Structure
-
-In "Bulk Edit" mode all suites and tests are presented in YAML format.
-
-![image](./images/107280279-cc2f7900-6a60-11eb-80fb-5c29d105ee2f.png)
-
-It may be hard to understand it from start.
-Let's explain it step by step:
-
-- On the top-level we have a list of suites:
-- Each element on the top level should start with `- ` char to indicate that it is a part of suites list.
-- Suites are defined as objects in YAML
-- A new suite should start with `suite:` key
-
-```yaml
-- suite: A new suite
-```
-
-- Existing suite starts with `S` char plus a suite ID, similarly to this:
-
-```yaml
-- S12345678: Existing suite
-```
-
-- A suite can contain other suites under `suites` key of the same object. Inside it you can have a list of child suites:
-
-```yaml
-- S12345678: Existing suite
-  suites:
-    - S22345678: Existing sub-suite 1
-    - suite: New sub-suite 2
-    - suite: New sub-suite 3
-```
-
-- A sub-suite can also contain a list of suites... Now you may see the power of YAML format!
-
-```yaml
-- S12345678: Existing suite
-  suites:
-    - S22345678: Existing sub-suite 1
-      suites:
-        - suite: A new sub-sub-suite!
-```
-
-> Please note that we indent our data with 2 spaces (`  `) to indicate which level we are at. We got down to 3rd level in this example, so we used 6 spaces before `- suite: A new sub-sub-suite!`
-
-- A suite may contain tests under `tests` key. Tests should be also represented as a list. If a test has `test:` key or no key at all, it is treated as a new test:
-
-```yaml
-- suite: User Management
-  tests:
-    - test: A new test 1
-    - A new test 2 # short format
-```
-
-> This structure creates 2 new tests under the new suite "User Management"
-
-- Existing test starts with `T` char plus a test ID, similarly to this:
-
-```yaml
-- S12345678: Existing suite
-  tests:
-    - T12345679: Existing test
-```
-
-- to delete a test or a suite - remove it from the structure
-- to change the order of tests or suites - move them up or down in the structure
-
-These rules are important to keep in mind when working in Bulk Edit mode.
-
-Let's sum up what we learned so far:
-
-- listing existing suites and tests
-
-![Listing existing suites and tests](./images/SuiteID-TestID.png)
-
-- adding new tests and suites:
-
-![image](./images/Bulk_edit_adding_elements.png)
-
-## Keyboard Shortcuts
-
-To unleash the full power of bulk edit learn these keyboard combinations that will speed up your work.
-
-- Use **Alt+Up** to move current line one level higher.
-- Use **Alt+Down** to move one level lower.
-
-![move-elements](./images/107283660-5bd72680-6a65-11eb-8235-5ea701818858.gif)
-
-- Also you may select a block of text and move it with **Alt+Up** or **Alt+Down**
-
-![move-suite](./images/107283762-7e693f80-6a65-11eb-8791-1ec1a73fca04.gif)
-
-- Use **Cmd+Right** or **Ctrl+Right** to indent a block to move it to next nesting level
-
-![move-indent](./images/107283909-b07aa180-6a65-11eb-8f7a-277e4c5390a2.gif)
-
-- Use **Cmd+d** or **Ctrl+d** to make a multiple selection. This allows replace values on the fly.
-
-![replace](./images/107284209-1830ec80-6a66-11eb-9737-3e672ff149d3.gif)

package/skills/testeiya/testomatio-docs/docs/advanced/jira-plugin/branches.md

@@ -1,53 +0,0 @@
----
-title: Work with Branches in Jira
-description: Learn how to manage branches in the Testomat.io Jira plugin. This guide covers creating new branches, switching between branches and the main project, and working with tests and suites within branches directly in Jira.
-type: article
-url: https://docs.testomat.io/advanced/jira-plugin/branches
-head:
-  - tag: meta
-    attrs:
-      name: keywords
-      content: Jira plugin, Testomat.io, branches, manage branches, test branches, Jira branches, work with branches, test management, BDD, feature files, Jira integration
----
-
-With the Testomat.io Jira Plugin, you can manage branches directly from Jira. This allows you to organize your tests and suites for different features or releases. Namely, you can:
-
-- Add new branches to the existing project
-- Switch between branches, including the Main branch
-- Make changes within existing branches
-
-## How To Create a New Branch
-
-1. Click on the **Branches** button
-2. Enter a branch name or leave it as the issue name
-3. Press **Enter**
-
-![Save a new branch](./images/att11_401.png)
-
-Your branch has been created successfully, and you are automatically switched to the newly created branch.
-
-![Created branch](./images/att12_401.png)
-
-## How to Switch Between Branches
-
-You can switch between branches and Main.
-
-1. Click on the **Branches** button
-2. Select the branch you want to switch to (e.g., **Switch to Main**)
-
-![Switch to Main](./images/att13_401.png)
-
-## How To Work Within Branches
-
-Within a branch, you can perform all actions available in Jira Plugin after logging in:
-
-- View linked tests and suites
-- Edit tests and suites directly
-- Unlink items if needed
-- Edit BDD Feature Files
-
-Tests and suites related to the current branch will be marked with a badge showing the branch name.
-
-[Learn more about what you can do after logging in](https://docs.testomat.io/advanced/jira-plugin#what-you-can-do-after-logging-in).
-
-![Branch badge](./images/att40_401.png)