# GitHub Actions Setup Guide

## Manual Release Workflow Configuration

This guide explains how to enable the manual release workflow for this repository.

## Problem

When running the Manual Release workflow, you may encounter permission errors:

```
remote: Permission to link-foundation/test-anywhere.git denied to github-actions[bot].
```

or

```
GitHub Actions is not permitted to create or approve pull requests.
```

## Solution

The workflow requires **two separate configurations** to function properly:

### 1. Workflow Permissions ✅ (Already Configured)

The workflow files already include:

```yaml
permissions:
  contents: write
  pull-requests: write
```

This grants the workflow job permission to write to the repository and create pull requests.

### 2. Repository Settings ⚠️ (Requires Manual Action)

**Repository administrators must enable GitHub Actions to create pull requests:**

> **⚠️ IMPORTANT:** If your repository belongs to an organization, you must configure these settings at **BOTH** the organization level AND the repository level. Organization settings can restrict repository-level permissions, so if you cannot enable these options in repository settings, check your organization settings first.

#### Steps for Repository Settings:

1. Navigate to your repository on GitHub
2. Click **Settings** (top navigation)
3. Click **Actions** → **General** (left sidebar)
4. Scroll down to **Workflow permissions** section
5. Select: ☑️ **"Read and write permissions"**
6. Check the box: ☑️ **"Allow GitHub Actions to create and approve pull requests"**
7. Click **Save**

#### Steps for Organization Settings (if applicable):

If the repository-level option **"Allow GitHub Actions to create and approve pull requests"** is disabled or grayed out, you need organization-level permissions:

1. Navigate to your **Organization** page on GitHub (e.g., `github.com/orgs/link-foundation`)
2. Click **Settings** (organization settings)
3. Click **Actions** → **General** (left sidebar)
4. Scroll down to **Workflow permissions** section
5. Select: ☑️ **"Read and write permissions"**
6. Check the box: ☑️ **"Allow GitHub Actions to create and approve pull requests"**
7. Click **Save**
8. **Then return to repository settings** and verify the option is now available

#### Visual Guide:

**Repository Settings:**

```
Repository → Settings → Actions → General
  └── Workflow permissions
      ├── ○ Read repository contents and packages permissions
      └── ● Read and write permissions  ← SELECT THIS
          └── ☑️ Allow GitHub Actions to create and approve pull requests  ← CHECK THIS
```

**Organization Settings (if needed):**

```
Organization → Settings → Actions → General
  └── Workflow permissions
      ├── ○ Read repository contents and packages permissions
      └── ● Read and write permissions  ← SELECT THIS
          └── ☑️ Allow GitHub Actions to create and approve pull requests  ← CHECK THIS
```

## Why Multiple Configurations Are Required

| Configuration                        | Purpose                                                                     |
| ------------------------------------ | --------------------------------------------------------------------------- |
| Workflow permissions                 | Grants the specific workflow job write access to the repository             |
| Repository setting                   | Allows the `github-actions[bot]` account to create PRs in this repo         |
| Organization setting (if applicable) | Allows the `github-actions[bot]` account to create PRs across all org repos |

For repositories created after **February 2, 2023**, GitHub Actions has read-only permissions by default for security reasons.

**Settings Hierarchy:**

- **Organization settings override repository settings**
- If organization settings restrict PR creation, repository-level settings will be disabled/grayed out
- Both levels must allow PR creation for the workflow to succeed

## Testing the Fix

Once the repository setting is enabled:

1. Go to **Actions** tab
2. Select **Manual Release** workflow
3. Click **Run workflow** button
4. Fill in the form:
   - **Release type**: patch/minor/major
   - **Description**: (optional) Description of changes
5. Click **Run workflow**

**Expected Result:**

- Workflow creates a new branch named `changeset-manual-release-{run_id}`
- A changeset file is added to `.changeset/` directory
- A pull request is automatically created with release details

## Troubleshooting

### Still Getting 403 Errors?

1. **Verify workflow permissions** in workflow files:

   ```yaml
   jobs:
     create-changeset:
       permissions:
         contents: write
         pull-requests: write
   ```

2. **Verify repository settings**:
   - Settings → Actions → General → Workflow permissions
   - Both "Read and write" and "Allow PR creation" must be enabled

3. **Check organization settings** (if applicable):
   - **IMPORTANT:** Organization settings can override repository settings
   - Navigate to your organization's Settings → Actions → General
   - Verify that "Allow GitHub Actions to create and approve pull requests" is enabled at the organization level
   - Contact your organization administrator if you don't have access to these settings

### Repository-Level Setting is Disabled/Grayed Out?

This indicates that organization-level policies are restricting repository settings:

1. **Check organization permissions:**
   - You need organization owner or admin access to change organization-level Actions settings
   - Navigate to `github.com/orgs/YOUR_ORG_NAME/settings/actions`

2. **Enable at organization level first:**
   - Enable "Read and write permissions"
   - Enable "Allow GitHub Actions to create and approve pull requests"
   - Save changes

3. **Return to repository settings:**
   - The repository-level option should now be available
   - Enable it at the repository level as well

### Workflow Runs But PR Not Created?

- Check the workflow logs in the Actions tab
- Verify the `peter-evans/create-pull-request` step completed successfully
- Ensure you have the latest version of the action (v7)

## Related Documentation

- [GitHub Actions Token Permissions](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token)
- [peter-evans/create-pull-request Action](https://github.com/peter-evans/create-pull-request)
- [Managing GitHub Actions Settings](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)

## Support

If you continue to experience issues after following this guide, please:

1. Check the [issue tracker](../../issues)
2. Review the [workflow logs](../../actions)
3. Create a new issue with detailed error messages
