docs: add v1.3 pages for CE (#381)

## 📝 Description
This PR adds v1.3 pages for CE.

In addition, it adds the following small changes:

- note on exporting audit logs in CSV format
(#353)
- note about inviting GitHub and BitBucket users
(#354)
- note about GitHub users being case-sensitive
(#355)
- note about GitHub PRs stuck due to renamed pipelines
(#360)

## ✅ Checklist
- [X] I have tested this change
- [ ] This change requires documentation update

Author: TomFern

docs/docs/getting-started/faq.md

@@ -419,6 +419,10 @@ If you cannot authenticate, you can use other third-party Docker registries such
 
 :::
 
+### Pull request on GitHub is stuck
+
+If you have a pull request stuck when using GitHub, check if you have renamed the pipeline recently. If you did, see how to [fix stuck PRs on GitHub](../using-semaphore/connect-github#stuck-pr)
+
 
 ## Project
 

docs/docs/using-semaphore/connect-github.md

@@ -178,6 +178,34 @@ This means that Semaphore can't fetch the `.semaphore/semaphore.yml` file from t
 1. **The file doesn't exist on your repository**: double check to make sure that the Semaphore YAML file actually exists
 2. **Repository is disconnected from Semaphore**: follow the steps [previously described](#reconnect)
 
+### This pull request is still a work in progress {#stuck-pr}
+
+Renaming the pipeline in Semaphore can cause GitHub pull requests to be stuck, as GitHub expects the old name to report back the status.
+
+For instance, renaming the `semaphore.yml` pipeline file from:
+
+```yaml
+version: v1.0
+name: Rails 7
+```
+
+To something like:
+
+```yaml
+version: v1.0
+name: Rails 8
+```
+
+Can cause any pending pull requests on GitHub to wait forever.
+
+To solve the issue, follow these steps:
+
+1. Go to your GitHub repository.
+2. Navigate to **Settings** > **Branches**,
+3. Under **Branch Protection Rules**, find the rule for your default or protected branch and press **Edit**
+4. In the **Require status checks to pass before merging** section, remove the outdated check, e.g. `ci/semaphoreci/push: old-name`) and add the new one if needed, e.g. `ci/semaphoreci/push: new-name`
+5. Save the changes.
+
 ## Connect with GitHub SAML
 
 Semaphore supports repositories hosted on GitHub with SAML single sign-on (SSO). This GitHub feature is available in the GitHub Enterprise Cloud offering.

docs/docs/using-semaphore/organizations.md

@@ -80,7 +80,8 @@ To invite a user to your organization, press the **Add people** button:
 <Steps>
 
 1. Select one of the available tabs
-    - Type the user's handle, e.g. `TomFern`, or select the user from the list.
+
+    - Type the user's handle, e.g. `TomFern`, or select the user from the list. Usernames are case-sensitive and all characters are considered. Ensure the handle is entered accurately to avoid errors.
     - If you don't see the user in the list. Ensure they have repository access in **GitHub** or **BitBucket** for at least one project in your organization
 
     ![Invite users](./img/invite-users.jpg)
@@ -91,6 +92,14 @@ To invite a user to your organization, press the **Add people** button:
 
 </Steps>
 
+:::info
+
+If you see an error with the message "error finding USERNAME: 401", it's likely that the your Semaphore account, as the inviter, is no longer linked to GitHub or BitBucket.
+
+To fix the issue, reconnect your account by granting access again via [GitHub](./connect-github-oauth#connect-oauth) or [Bitbucket](./connect-bitbucket#grant-bb). This should restore your ability to send invitations.
+
+:::
+
 ### How to remove users {#remove-users}
 
 Users can only be removed from the organization when they don't own any projects. You must [transfer the ownership](./projects#owner-change) of all the user's projects before they can be removed from the organization.
@@ -333,6 +342,8 @@ To configure streaming to an S3-compatible bucket, press the **Configure Streami
 
 Audit logs are streamed to the bucket once per day.
 
+Large audit logs may cause errors when exporting to CSV. In this case, consider setting up an S3-compatible bucket instead of using CSV as the export medium.
+
 :::
 
 ## Organization queues {#queue}

docs/docusaurus.config.js

@@ -65,10 +65,14 @@ const config = {
               banner: "none",
             },
             "CE": {
-              label: 'Community Edition v1.2',
+              label: 'Community Edition v1.3',
               path: 'CE',
               banner: "none"
             },
+            "CE-1.2": {
+              label: 'Community Edition v1.2',
+              path: 'CE-1.2',
+            },
             "CE-1.1": {
               label: 'Community Edition v1.1',
               path: 'CE-1.1',

docs/versioned_docs/version-CE-1.2/getting-started/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Get Started",
+  "position": 1,
+  "link": {
+    "type": "generated-index",
+    "description": "Guided tour and the basics of Continuous Integration and Delivery (CI/CD)"
+  }
+}

docs/versioned_docs/version-CE-1.2/getting-started/about-semaphore.md

@@ -0,0 +1,40 @@
+---
+description: About Semaphore
+---
+
+# About Semaphore
+
+Semaphore is [Continuous Integration and Delivery](https://semaphore.io/continuous-integration) (CI) platform that's fast, easy to use, and incredibly scalable. 
+
+## Semaphore editions {#editions}
+
+Semaphore comes in two editions:
+
+- **[Semaphore Cloud](/getting-started/about-semaphore)**: is a cloud-based, fully-managed CI-as-a-Service platform. Meant for individuals and companies that don't wish to maintain a CI/CD system. Head to [semaphoreci.com](https://semaphore.io) to access Semaphore Cloud
+- **[Semaphore CE](/CE/getting-started/install)**: is the free and open-source Community Edition of Semaphore. Meant for anyone that wishes to host and manage their own CI/CD architecture.
+- **On-premise (Enterprise Edition)**: fully-featured Semaphore that can run behind a firewall using your infrastructure
+
+See the [feature comparison](./features) to decide which edition of Semaphore is best for you.
+
+## What is CI/CD?
+
+Continuous Integration (CI) is an automated process of regularly merging code changes, running tests, and providing rapid feedback to developers.
+
+CI enables developers to frequently merge code changes, automatically test them, and detect integration issues early, leading to faster development cycles and higher-quality software.
+
+![CI Workflow](./tour/img/ci-workflow.jpg)
+
+Continuous Delivery and Continuous Deployment extend this process by providing a package you can release and deploy to the world. The whole thing is automated and can be set up to not need human intervention. No more stressing over deployment or releases!
+
+![CD Workflow](./tour/img/cd-workflow.jpg)
+
+## Where to go next?
+
+If you want to give Semaphore Cloud, head to the [Guided Tour](./guided-tour). If you prefer to self-host, see the [Community Edition installation guide](./install).
+
+You can find the complete Semaphore handbook in the [Using Semaphore](../using-semaphore/jobs) section.
+
+And if you want to dive deep into Semaphore's inner workings check out the [Reference pages](../reference/semaphore-cli) and the [Semaphore API reference](../reference/api).
+
+<!-- new api: [API documentation](../openapi-spec/semaphore-public-api.info.mdx) --->
+

docs/versioned_docs/version-CE-1.2/getting-started/changelog.md

@@ -0,0 +1,9 @@
+---
+description: Semaphore change log for Semaphore CE.
+---
+
+# Change Log
+
+Thank you for using Semaphore!
+
+This page shows changes in all Semaphore CE versions.

docs/versioned_docs/version-CE-1.2/getting-started/experiments.md

@@ -0,0 +1,46 @@
+# Experiments Sandbox (dev build)
+
+## Steps
+
+
+import Steps from '@site/src/components/Steps';
+
+```js
+import Steps from '@site/src/components/Steps';
+```
+
+<Steps>
+
+
+1. Import the component into your MDX file:
+
+   ```js
+   import Steps from '@site/src/components/Steps';
+   ```
+2. Step 2
+
+    - subpoint
+    - subpoint
+    - subpoint
+
+    <details>
+    <summary>Show me</summary>
+    <div>
+
+    Surprise!
+
+    </div>
+    </details>
+
+3. Another step
+
+    ```yaml
+    key: value
+    ```
+4. Image
+
+    ![Test](../using-semaphore/img/account-gh-bb-access.jpg)
+
+5. Finish
+
+</Steps>